On Mon, Apr 13, 2015 at 5:25 PM, Chris Barker <chris.bar...@noaa.gov> wrote:
> On Mon, Apr 13, 2015 at 1:19 PM, David Cournapeau <courn...@gmail.com> > wrote: > >> This is what we use on top of setuptools egg: >> >> - ability to add dependencies which are not python packages (I think >> most of it is already handled in metadata 2.0/PEP 426, but I would have to >> re-read the PEP carefully). >> - ability to run post/pre install/remove scripts >> - support for all the of the autotools directories, with "sensible" >> mapping on windows >> > > Are these inside or outside the python installation? I'm more than a bit > wary of a wheel that would install stuff outside of the "sandbox" of the > python install. > I would always install things relative to sys.prefix, for exactly the reasons you mention. > > > The whole reason I started this discussion is to make sure wheel has a >> standard way to do what is needed for those usecases. >> >> conda, rpm, deb, or eggs as used in enthought are all essentially the >> same: an archive with a bunch of metadata. The real issue is standardising >> on the exact formats. As you noticed, there is not much missing in the >> wheel *spec* to get most of what's needed. > > > hmm -- true. I guess where it seems to get more complicated is beyond the > wheel (or conda, or...) package itself, to the dependency management, > installation tools, etc. > > But perhaps you are suggesting that we can extend wheel to support a bt > more stuff, and leave the rest of the system as separate problem? i.e. > Canopy can have it's own find, install, manage-dependency tool, but that it > can use the wheel format for the packages themselves? > Exactly ! David
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig