Skip to content
New issue

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

Innacurate/out of date information #276

Closed
danielquinn opened this issue Jan 13, 2017 · 2 comments
Closed

Innacurate/out of date information #276

danielquinn opened this issue Jan 13, 2017 · 2 comments

Comments

@danielquinn
Copy link

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:

      $ python setup.py bdist_wheel
      usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
         or: setup.py --help [cmd1 cmd2 ...]
         or: setup.py --help-commands
         or: setup.py cmd --help
      
      error: invalid command 'bdist_wheel'
    
  • Uploading via twine appears to work, but if you don't use twine, it doesn't work at all:

      $ python setup.py sdist upload
      error: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590)>
    

    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?

@jwodder
Copy link
Contributor

jwodder commented Jan 14, 2017

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.

@theacodes
Copy link
Member

This should be resolved as of #271, but if it isn't, let me know @danielquinn!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants