Re: [Distutils] What role to eggs still play?

On Wed, Aug 24, 2016 at 1:28 PM Leonardo Rochael Almeida < leoroch...@gmail.com> wrote: > On 24 August 2016 at 12:56, Daniel Holth wrote: > >> On Wed, Aug 24, 2016 at 10:41 AM Alex Grönholm >> wrote: >> > [...] >>> >> >> 19.08.2016, 20:25, Daniel

Re: [Distutils] What role to eggs still play?

On 24 August 2016 at 12:56, Daniel Holth wrote: > On Wed, Aug 24, 2016 at 10:41 AM Alex Grönholm > wrote: > >> [...] >> > > 19.08.2016, 20:25, Daniel Holth kirjoitti: > > Eggs are the only way to add a zipped distribution to PYTHONPATH and have >

Re: [Distutils] What role to eggs still play?

On Wed, Aug 24, 2016 at 10:41 AM Alex Grönholm wrote: > 20.08.2016, 01:41, Chris Barker - NOAA Federal kirjoitti: > > Thanks, I think I'm getting it. > > About the toml file... the *-info metadata is a compiled artifact, > according to all the existing Python packages.

Re: [Distutils] What role to eggs still play?

20.08.2016, 01:41, Chris Barker - NOAA Federal kirjoitti: Thanks, I think I'm getting it. About the toml file... the *-info metadata is a compiled artifact, according to all the existing Python packages. Most sdists even have a *.egg-info directory. If it's a compiled artifact, then

Re: [Distutils] What role to eggs still play?

19.08.2016, 20:25, Daniel Holth kirjoitti: Eggs are the only way to add a zipped distribution to PYTHONPATH and have setuptools find the metadata (the Python code can be found with or without the metadata; setuptools does not discover *.dist-info inside zip). Eggs are used by buildout,

Re: [Distutils] What role to eggs still play?

Pip uses pkg-resources to enumerate the installed packages. An advantage of building the installation metadata is when you decide to change the format, like by adding toml for example  On Fri, Aug 19, 2016, 18:41 Chris Barker - NOAA Federal < chris.bar...@noaa.gov> wrote: > Thanks, I think I'm

Re: [Distutils] What role to eggs still play?

Thanks, I think I'm getting it. About the toml file... the *-info metadata is a compiled artifact, according to all the existing Python packages. Most sdists even have a *.egg-info directory. If it's a compiled artifact, then shouldn't it NOT be in a source dist? It is inconvenient if you want

Re: [Distutils] What role to eggs still play?

About the toml file... the *-info metadata is a compiled artifact, according to all the existing Python packages. Most sdists even have a *.egg-info directory. It is inconvenient if you want to know the true dependencies without running setup.py. I think we are stuck with it, and it's not all bad

Re: [Distutils] What role to eggs still play?

Eggs are the only way to add a zipped distribution to PYTHONPATH and have setuptools find the metadata (the Python code can be found with or without the metadata; setuptools does not discover *.dist-info inside zip). Eggs are used by buildout, especially in the unzipped into a directory form. And

Re: [Distutils] What role to eggs still play?

> On Aug 19, 2016, at 12:53 PM, Chris Barker wrote: > > Hi all, > > starting a new thread, but this is related to the setuptols-_lite discussion, > and the legacy formats discussion. In another thread Donald had a footnote: > > > [1] We can tackle egg at a later

[Distutils] What role to eggs still play?

Hi all, starting a new thread, but this is related to the setuptols-_lite discussion, and the legacy formats discussion. In another thread Donald had a footnote: [1] We can tackle egg at a later point, when setuptools either has support > for Wheels > or is less needed. So I'm wondering