Mailman 3 July 2017 - Distutils-SIG

PEP 420 on python2
by Asmodehn Shade 15 Jul '17

15 Jul '17

Hi everyone, I m very new around here, I just wanted to let you know that while writing a custom importer for py2 and py3, I ended up backporting some python3 libimport code to python2. The code is over there : https://github.com/asmodehn/filefinder2 This way I now support importing packages without __init__.py in python2. It was simpler for my usecase than using pkg_resources or pkgutil. So if anyone is interested in that, let me know, while I still have my head around this. Cheers ! -- AlexV

2 3

Upload documentation to be hosted at ‘pythonhosted.org’
by Ben Finney 14 Jul '17

14 Jul '17

Howdy all, Is ‘pythonhosted.org’ still a recommended service for hosting documentation for Python distributions? It certainly seems so, from the page at <URL:https://pythonhosted.org/>: This site hosts documentation uploaded by authors of packages in the Python Package Index. To upload documentation, go to your package edit page (http://pypi.python.org/pypi?%3Aaction=pkg_edit&name=yourpackage), and fill out the form at the bottom of the page. Should that change for the fact that ‘pypi.python.org’ is in the process of deprecation for uploads? -- \ “If nature has made any one thing less susceptible than all | `\ others of exclusive property, it is the action of the thinking | _o__) power called an idea” —Thomas Jefferson, 1813-08-13 | Ben Finney

2 2

how sdist generation works in enscons
by Daniel Holth 06 Jul '17

06 Jul '17

Here's how sdist generation works in enscons. enscons, a build tool that exists to prototype new Python packaging features, is just a set of tools for SCons that makes it easier to generate wheels and sdists. If targets with certain names exist (sdist, bdist_wheel) then the provide setup.py shim and new PEP 517 wrapper will interoperate with pip. For enscons itself, the sdist build rule looks like sdist = env.SDist(source=FindSourceFiles() + ['PKG-INFO', 'setup.py', 'README.rst', 'CHANGES'])env.Alias('sdist', sdist) Enscons would be able to build its own sdist outside a repository, and it would include the listed files plus everything that is used to build the other targets (the wheel). A different package runs 'hg manifest' in a subprocess to feed to env.SDist(), a natural thing to do in this kind of build system. That one would not be able to build another sdist from an unpacked sdist. Enscons itself doesn't have a way to know whether sdist generation will succeed other than trying to run 'SCons sdist' against the user provided build script.

2 1