Menu
Python 3.3 will come with a new packaging tool called "packaging":
The new "packaging" module, building upon the "distribute" and "distutils2" projects and deprecating "distutils"
Does this mean that Distribute will be outdated with Python 3.3?
628
Distribution Package. A versioned archive file that contains Python packages, modules, and other resource files that are used to distribute a Release. The archive file is what an end-user will download from the internet and install.
In order to create a Python package, you need to write the code that implements the functionality you want to put in your package, and then you need to publish it to PyPI. That is the bare minimum.
Use PyInstaller, py2exe, Nuitka, or another bundling solution. The most convenient way to deliver a Python application to a user is to provide them with an executable—either a single file or a directory with an easily identified executable somewhere in it.
The 3.3 release notes are a bit misleading: packaging is distutils2, and it does not build upon distribute but imitates some features, but with different behavior or specification, especially for the parts that have been standardized with PEP 376, 386 and 345, and with very different code and usage.
For end users, in a way distutils2/packaging don’t make distribute outdated, as distribute still provides unique features, but from another viewpoint it is obsoleted, as it does not support the current PEPs and is not officially supported (i.e. in the stdlib).
Regarding the various packaging projects, I think the distribute devs plan to support the new PEPs, and I don’t know about setuptools. pip and buildout will use distutils2 instead of distribute as underlying library in the longer term.
150
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
