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
I'm trying to follow the proper process for creating a package and am having far too much trouble.
The package submission page on the current site lists the installation preference of twine, register, and web form.
The documentation that page points to tells you to use a web form to create an account, upload a PKG-INFO file via another form, but use twine for everything else while defining a ~/.pypirc file that points to https://upload.pypi.org/legacy/.
The page also tells me to use bdist_wheel when creating my package, but bdist_wheel isn't listed as one of the options when I execute python setup.py --help-commands:
I note that the docs say "not recommended" but I took that to mean "use this if your system doesn't have a package for twine. It'll work, just not as nicely".
From much digging around the web I see references to older versions of Python 2 not checking certificates and that a downgrade is the recommended solution in this case (though I don't see the logic there). As I'm currently using Python 3.4 that wasn't going to happen.
As my distro (Gentoo) doesn't have a package for twine, I had to install it into my virtualenv to deploy a package unrelated to it. This is annoying, but manageable. The real problem for me is that the documentation refers to using upload and bdist_wheel as these are apparently impossible with modern versions of Python?
The text was updated successfully, but these errors were encountered:
bdist_wheel is possible with all modern versions of Python. The reason your setup.py doesn't recognize it is because you either (a) don't have the wheel package installed or (b) are using distutils instead of setuptools.
I'm trying to follow the proper process for creating a package and am having far too much trouble.
The package submission page on the current site lists the installation preference of twine, register, and web form.
The documentation that page points to tells you to use a web form to create an account, upload a PKG-INFO file via another form, but use twine for everything else while defining a ~/.pypirc file that points to
https://upload.pypi.org/legacy/
.The page also tells me to use
bdist_wheel
when creating my package, but bdist_wheel isn't listed as one of the options when I executepython setup.py --help-commands
:Uploading via twine appears to work, but if you don't use twine, it doesn't work at all:
I note that the docs say "not recommended" but I took that to mean "use this if your system doesn't have a package for twine. It'll work, just not as nicely".
From much digging around the web I see references to older versions of Python 2 not checking certificates and that a downgrade is the recommended solution in this case (though I don't see the logic there). As I'm currently using Python 3.4 that wasn't going to happen.
As my distro (Gentoo) doesn't have a package for twine, I had to install it into my virtualenv to deploy a package unrelated to it. This is annoying, but manageable. The real problem for me is that the documentation refers to using
upload
andbdist_wheel
as these are apparently impossible with modern versions of Python?The text was updated successfully, but these errors were encountered: