You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My knowledge of packaging conventions may be out of date, but I understand that directly invoking setup.py is something users should migrate away from since a) in the future it may disappear entirely and b) it has various historical quirks.
The docs for wheel still showpython setup.py bdist_wheel as the way to build wheels. Should they be updated to call pip wheel . instead? Or is there some intended difference between these two commands?
The text was updated successfully, but these errors were encountered:
The wheel docs are not the authoritative documentation for Python packaging. The authoritative documentation can be found at packaging.python.org. I will review the wheel docs and update as necessary when I am done with the more urgent work in my other projects.
They should show pipx run build --wheel or python -m pip install build && python -m build --wheel, I think. They probably shouldn't show setup.py commands (https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html), but then again, this is likely more focused on how things work for developers more than user facing docs. Internally, that's still the command name, even if users shouldn't be running it.
My knowledge of packaging conventions may be out of date, but I understand that directly invoking
setup.py
is something users should migrate away from since a) in the future it may disappear entirely and b) it has various historical quirks.The docs for wheel still show
python setup.py bdist_wheel
as the way to build wheels. Should they be updated to callpip wheel .
instead? Or is there some intended difference between these two commands?The text was updated successfully, but these errors were encountered: