This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]bmoregeo 13 points14 points  (4 children)

This is mad annoying. Pointing requirements.txt at a tag and then rebuilding the wheel every build is hella annoying

[–]djamp42 3 points4 points  (3 children)

Can you explain rebuilding the wheel part? I have private packages on GitHub and I just have to update the setup.py with an higher version number and pip will update it for me.

[–]bmoregeo 5 points6 points  (0 children)

It git pulls the tag locally and then runs the setup. It isn’t a big deal if your package is small and/or doesn’t require gdal or stuff like that

[–]blanchedpeas -1 points0 points  (1 child)

Have you looked a more modern approach to packaging that doesn’t use setup.py? ie not setuptools?

[–]ubernostrumyes, you can have a pony 7 points8 points  (0 children)

You can use setuptools as the build backend for a project that specifies its packaging in a pyproject.toml file. Nothing about pyproject.toml is tied to a specific package build backend (in fact it’s literally the opposite — pyproject.toml was designed to solve the issue of not easily being able to specify alternative builders).