Python wheels deployment documentation is incorrect about dpl HOT 7 CLOSED

Just to make sure I get it right, it should be bdist_wheels instead of just bdist?

from dpl.

I think so. At least this code says so.

from dpl.

Oh, I have a typo in the issue description. It should be bdist_wheel instead of bdist_wheels

from dpl.

http://guide.python-distribute.org/contributing.html seems to say that bdist is OK. Am I missing something? Granted, I am not familiar with the Python ecosystem.

from dpl.

This is quite confusing.

According to these docs:

• http://packaging.python.org/en/latest/tutorial.html#building-packaging-your-project
• http://wheel.readthedocs.org/en/latest/index.html

It should be bdist_wheel

from dpl.

Hello.

These days, bdist_wheel is preferred to bdist. However the default should just be to upload sdists. Anything extra should be a devs choice.

bdist_wheel produces a .whl and is good for pure python packages, but problematic for packages with extensions modules. See the third paragraph of "What are wheels": http://lucumr.pocoo.org/2014/1/27/python-on-wheels/.

bdist_egg produces a .egg. This is an older format that wheels. Pypi supports both, but pypa (the group of devs behind pypi/pip/virtualenv) strongly advocate wheels over eggs.

bdist produces a .tar.gz. (With --formats it can produce quite a few different formats...).

The bdist/bdist_wheel family of builds is more useful on Mac or Windows machines, where it can be more awkward to get a fully functional toolchain. You can ship precompiled binary extensions easily.

from dpl.

Thanks for clearing it up!

from dpl.