We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi!
Please could this package also by made available as a wheel on PyPI? https://pypi.python.org/pypi/slugid/1.0.7
Wheels have the following advantages:
This package is pure Python and supports both Python 2 and 3, so can be distributed as a "universal wheel": https://packaging.python.org/tutorials/distributing-packages/#wheels
To save having to pass --universal to setup.py each time, the pref can be saved in setup.cfg:
--universal
setup.py
setup.cfg
[bdist_wheel] universal=1
The Python packaging guide recommends using Twine to upload packages: https://packaging.python.org/tutorials/distributing-packages/#uploading-your-project-to-pypi
So with the setup.cfg as above, the steps for building/uploading a new release are then:
$ pip install -U twine setuptools wheel $ rm -rf dist/ build/ $ python setup.py sdist bdist_wheel $ twine upload dist/*
The PyPI package listing will then display two entries for the new release, one with type "Source" and the other "Python Wheel".
Many thanks :-)
The text was updated successfully, but these errors were encountered:
I don't suppose you could push the wheel for 1.0.7, or else generate a 1.0.8 with both wheel and sdist? :-)
Sorry, something went wrong.
No branches or pull requests
Hi!
Please could this package also by made available as a wheel on PyPI?
https://pypi.python.org/pypi/slugid/1.0.7
Wheels have the following advantages:
This package is pure Python and supports both Python 2 and 3, so can be distributed as a "universal wheel":
https://packaging.python.org/tutorials/distributing-packages/#wheels
To save having to pass
--universal
tosetup.py
each time, the pref can be saved insetup.cfg
:The Python packaging guide recommends using Twine to upload packages:
https://packaging.python.org/tutorials/distributing-packages/#uploading-your-project-to-pypi
So with the
setup.cfg
as above, the steps for building/uploading a new release are then:$ pip install -U twine setuptools wheel $ rm -rf dist/ build/ $ python setup.py sdist bdist_wheel $ twine upload dist/*
The PyPI package listing will then display two entries for the new release, one with type "Source" and the other "Python Wheel".
Many thanks :-)
The text was updated successfully, but these errors were encountered: