Le lundi 22 octobre 2012 à 16:25 -0400, Daniel Holth a écrit : > On Mon, Oct 22, 2012 at 4:13 PM, Antoine Pitrou <solipsis at pitrou.net> wrote: > > On Mon, 22 Oct 2012 15:39:07 -0400 > > Daniel Holth <dholth at gmail.com> wrote: > >> On Mon, Oct 22, 2012 at 3:27 PM, Antoine Pitrou <solipsis at pitrou.net> wrote: > >> > > >> > Hello, > >> > > >> > How does the pure / plat distinction as outlined in PEP 427 cope with > >> > Debian's system of separating installed files into pyshared (for *.py > >> > and *.egg-info files) and pythonX.Y/dist-packages (for *.pyc and *.so > >> > files)? > >> > > >> > Thanks, > >> > > >> > Antoine. > >> > >> It is only there because distutils has a purelib/platlib distinction, > >> so the spec represents it. See > >> http://hg.python.org/cpython/file/49de26395d1a/Lib/distutils/command/install.py#l85 > > > > Ok, so does this mean Debian would have to build their own installer if > > they want to spread the wheel's contents as appropriate for their > > directory layout? > > Sorry if this is a lame observation, but Debian has already built > their own installer called dpkg. Right :) > The Python-specific binary format will mainly be used to populate > virtualenvs. It may also turn out to be a convenient intermediate step > to build an .rpm or .deb but that is not the primary design goal. Well, I would expect people to also use it for regular installations, especially under Windows (thanks to the ABI tag for extension modules). Regards Antoine.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4