Re: Indeed, python-concurrent.futures is the same
On Sat, Jan 25, 2014 at 3:53 PM, Thomas Goirand <zigo@debian.org> wrote:
> I'm however confused how "import concurrent" works, even if there's
> nothing in /usr/lib/python2.7/dist-packages in this package. How come?
Take a look at /usr/share/doc/python-support/README.gz
> * Public modules (.py files that should be installed in the default
> sys.path) are handled through a foo.public file, which contains a
> list of files to install. The files are normally installed in
> /usr/share/pyshared/. They will be installed and bytecompiled in each
> Python specific directory: /usr/lib/pymodules/pythonX.Y/. If the header
> of the foo.public file contains a "pyversions=..." field, it will be
> parsed for the list of python versions the module supports. It should
> look like e.g.:
> 2.2,2.4-
> for a package supporting python2.2, and all versions starting from
> python2.4.
Also from Python Policy:
> Modules managed by python-support are installed in another directory
> which is added to the sys.path using the .pth mechanism.
https://www.debian.org/doc/packaging-manuals/python-policy/ch-python.html#s-paths
-- Andrew Starr-Bochicchio
Ubuntu Developer <https://launchpad.net/~andrewsomething>
Debian Developer <http://qa.debian.org/developer.php?login=asb>
PGP/GPG Key ID: D53FDCB1
Reply to: