Open KOLANICH opened 4 years ago
@KOLANICH Not sure how is this supposed to work? How do you build a package with this change?
setuptools has one of entry_points
used as a hook for other tools, setuptools_scm uses it. Should work out of the box as usual.
Did you tried it? What command do you use to build wheel and source distributions?
Did you tried it?
In fact I haven't tried building parglare for a while (it is installed with -e
for me), for other my tools I use the similar setuptools_scm
config in pyproject.toml
since support of this has been released.
What command do you use to build wheel and source distributions?
As usual python3 ./setup.py bdist_wheel
, but python3 -m pep517.build
(the new build-backend-independent command) should work too. What does it write for you?
As usual python3 ./setup.py bdist_wheel, but python3 -m pep517.build (the new build-backend-independent command) should work too. What does it write for you?
python setup.py bdist_wheel
doesn't pick up version correctly and produces package parglare-0.0.0-py2.py3-none-any.whl
. python -m pep517.build
does work after pip install pep517
. Do you have any reference what is the recommended way to do builds and uploads to PyPI now?
That's extremily strange. I have checked recently, on my machine everything works (I use python3
for building, python
2 is EOL). Please make sure that the libs (setuptools and setuptools_scm) are of the latest versions (pyproject.toml should ensure that the versions are compatible though) and that tag is present on the branch.
And improved stuff in setup.py a bit
Code review checklist
CHANGELOG.md
, no need to update for typo fixes and such).