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
The PyPI package listing will then display three entries for the new release, one with type "Source" and two of type "Python Wheel" (one for each of Python 2 and 3).
Many thanks :-)
The text was updated successfully, but these errors were encountered:
+1 for this one... as long as promise is only available as sdist and not as a bdist_wheel, we can't just use pip install --only-binary :all:... which is in turn a great mitigation for arbitrary code execution inherent to sdists. See https://github.com/mschwager/0wned
Hi!
Please could this package also by made available as a wheel on PyPI?
https://pypi.python.org/pypi/promise/2.0.2
Wheels have the following advantages:
This package is pure Python and supports both Python 2 and 3, so in theory could be distributed as a "universal wheel":
https://packaging.python.org/tutorials/distributing-packages/#wheels
...however I notice that there's some
__builtin__
vsbuiltins
workaround going on here:promise/setup.py
Lines 4 to 9 in 5177e53
...which I believe means separate wheels have to be generated for each of Python 2 and 3.
The Python packaging guide recommends using Twine to upload packages:
https://packaging.python.org/tutorials/distributing-packages/#uploading-your-project-to-pypi
As such, the steps for building/uploading a new release are then:
The PyPI package listing will then display three entries for the new release, one with type "Source" and two of type "Python Wheel" (one for each of Python 2 and 3).
Many thanks :-)
The text was updated successfully, but these errors were encountered: