Arch Linux

Greenstuff

Member

From: Israel

Registered: 2009-06-30

Posts: 70

Packeging a Python module with no setup.py

Hey,
This is my first time trying to package something in Arch. I tried looking at other pkgbuilds, as well as read the wiki article, but the package does not seem to contain a setup.py file, which is what most packages seem to use. The module in question is flopy, here is the github: https://github.com/modflowpy/flopy

Here is what I have so far. I wrote the following pkgbuild:

pkgname=('python-flopy')
pkgver=3.9.2
pkgrel=1
pkgdesc="A Python package to create, run, and post-process MODFLOW-based models. "
arch=('i686' 'x86_64')
url="flopy.readthedocs.io"
license=('CC0')
makedepends=('python' 
  'python-setuptools')
options=(!emptydirs)
source=("https://github.com/modflowpy/flopy/archive/refs/tags/3.9.2.tar.gz")
md5sums=('2a6363542323d7bd2e027a03050f6442')

build() {
  cd ${srcdir}/flopy-${pkgver}
  python setup.py build
}

package_python-flopy() {
  depends=('python')
  cd "$srcdir/flopy-$pkgver"
  python setup.py install --root=$pkgdir/ --optimize=1
}

This is what I get when trying to run this:

makepkg -f PKGBUILD   
==> Making package: python-flopy 3.9.2-1 (Sat Mar 29 20:17:46 2025)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found 3.9.2.tar.gz
==> Validating source files with md5sums...
    3.9.2.tar.gz ... Passed
==> Extracting sources...
  -> Extracting 3.9.2.tar.gz with bsdtar
==> Removing existing $pkgdir/ directory...
==> Starting build()...
python: can't open file '/home/gal/Code/Modflow/flopy-aur/src/flopy-3.9.2/setup.py': [Errno 2] No such file or directory
==> ERROR: A failure occurred in build().
    Aborting...

The problem is obviously that there is no setup.py file in this package. They only offer the option of installing using pip or conda. I was wondering how to get around this?

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,539

Re: Packeging a Python module with no setup.py

https://wiki.archlinux.org/title/Python … on_methods

There's a lot of other issues with the PKGBUILD right now, once you've got it working and polished, it would probably be good to ask for someone here to check it over.

Last edited by Scimmia (2025-03-29 17:37:57)

Greenstuff

Member

From: Israel

Registered: 2009-06-30

Posts: 70

Re: Packeging a Python module with no setup.py

https://wiki.archlinux.org/title/Python … on_methods

There's a lot of other issues with the PKGBUILD right now, once you've got it working and polished, it would probably be good to ask for someone here to check it over.

Thanks for this, I managed to get it to work, below is the packagebuild, I'd love it if people can give me feedback. I think since this package uses python-hatchling instead of python-wheel, there is no need for python-wheel or python-build in the makedepends array, am I right?

pkgname=('python-flopy')
pkgver=3.9.2
pkgrel=1
pkgdesc="A Python package to create, run, and post-process MODFLOW-based models. "
arch=('i686' 'x86_64')
url="flopy.readthedocs.io"
license=('CC0')
makedepends=('python' 
  'python-setuptools')
options=(!emptydirs)
source=("https://github.com/modflowpy/flopy/archive/refs/tags/3.9.2.tar.gz")
md5sums=('2a6363542323d7bd2e027a03050f6442')

makedepends=(python-hatchling python-hatch-fancy-pypi-readme python-build python-installer python-wheel)

_name=${pkgname#python-}

build() {
    cd $_name-$pkgver
    hatchling build 
}

package() {
    cd $_name-$pkgver
    python -m installer --destdir="$pkgdir" dist/*.whl
}

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,539

Re: Packeging a Python module with no setup.py

1. pkgname should generally only be an array in a split package setup.
2. You don't have a valid URL
3. That is not a valid SPDX license identifier
4. You should be using $pkgver in the source entry so you don't have to update the version in 2 places for updates.
5. You need to rename the source file to something unique. See the warning at https://wiki.archlinux.org/title/PKGBUILD#source
6. You have makedepends defined twice, making the first one useless
7. You're missing runtime dependencies.
8. This seems to be pure python? If there's nothing in the final package that's architecture specific, the arch array is wrong.
9. For your makedepends question, have you tried building in a clean chroot? You can remove the makedeps in question and see if it builds without them.

Greenstuff

Member

From: Israel

Registered: 2009-06-30

Posts: 70

Re: Packeging a Python module with no setup.py

1. pkgname should generally only be an array in a split package setup.
2. You don't have a valid URL
3. That is not a valid SPDX license identifier
4. You should be using $pkgver in the source entry so you don't have to update the version in 2 places for updates.
5. You need to rename the source file to something unique. See the warning at https://wiki.archlinux.org/title/PKGBUILD#source
6. You have makedepends defined twice, making the first one useless
7. You're missing runtime dependencies.
8. This seems to be pure python? If there's nothing in the final package that's architecture specific, the arch array is wrong.
9. For your makedepends question, have you tried building in a clean chroot? You can remove the makedeps in question and see if it builds without them.

Thank you. Why isn't the URL valid?

schard

Forum Moderator

From: Hannover

Registered: 2016-05-06

Posts: 2,215

Website

Re: Packeging a Python module with no setup.py

"flopy.readthedocs.io" is missing the protocol (https://)

---

Inofficial first vice president of the Rust Evangelism Strike Force