[Distutils] Proposed new Distutils API for compiler flag detection (Issue26689)

Some months ago, Sylvain brought up a couple of proposals for Distutils. The second proposal received some discussion but it appears that the first one got lost. Here it is: > From sylvain.corlay at gmail.com Wed May 25 12:01:51 2016 > From: sylvain.corlay at gmail.com (Sylvain Corlay) > Date

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] Deprecating little used file types/extensions on PyPI?

> On Aug 19, 2016, at 2:00 PM, Leonardo Rochael Almeida > wrote: > > ure, more people will be affected this way than just the folks releasing on > Windows, but given the shortcuts for setting the sdist format per project or > per home directory that Donald mentioned, I think the collective ef

Re: [Distutils] Deprecating little used file types/extensions on PyPI?

On 19 August 2016 at 14:14, Paul Moore wrote: > [...] > > So, the plan becomes: > > 1. Change Python 3.6 to default to .tar.gz on Windows > 2. Change setuptoos to default to .tar.gz, to catch users of older versions > 3. Document how to create a source distribution as "python setup.py > sdist (ad

Re: [Distutils] Deprecating little used file types/extensions on PyPI?

On 19 August 2016 at 18:21, Donald Stufft wrote: > FWIW, they can also drop a setup.cfg in their project too that looks > like: https://bpaste.net/show/90dd1280eba6 and then forget about it, which > makes it somewhat less painful, since they won’t have to remember to do it > on a per project basis

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 t

Re: [Distutils] Deprecating little used file types/extensions on PyPI?

> On Aug 19, 2016, at 1:14 PM, Paul Moore wrote: > > On 19 August 2016 at 16:14, Donald Stufft wrote: >> Not sure if we’ll be able to back port it to 2.7 itself, but it’s a trivial >> change to make inside of setuptools as well. Here’s a PR to setuptools that >> will adjust the default: https:/

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 point, when setuptools either

Re: [Distutils] Deprecating little used file types/extensions on PyPI?

On 19 August 2016 at 16:14, Donald Stufft wrote: > Not sure if we’ll be able to back port it to 2.7 itself, but it’s a trivial > change to make inside of setuptools as well. Here’s a PR to setuptools that > will adjust the default: https://github.com/pypa/setuptools/pull/748. Hmm. So the question

[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 --

Re: [Distutils] Future of setuptools and buildout

On Thu, Aug 18, 2016 at 10:17 PM, Wes Turner wrote: > setuptools does all of these, yes? but think of these in terms of when >> they come into play: >> >> build time: >>- building a package >> > > - building c extensions > - building NumPy (fortran,) > exactly! which is WHY we want/need more

Re: [Distutils] Deprecating little used file types/extensions on PyPI?

> On Aug 19, 2016, at 10:34 AM, Paul Moore wrote: > > On 19 August 2016 at 15:27, Donald Stufft wrote: >> This is an important consideration that nobody mentioned thus far— I have >> not used Windows to release a project to PyPI.. ever. So We should >> absolutely start by switching that to defa

Re: [Distutils] Deprecating little used file types/extensions on PyPI?

On 19 August 2016 at 15:27, Donald Stufft wrote: > This is an important consideration that nobody mentioned thus far— I have > not used Windows to release a project to PyPI.. ever. So We should > absolutely start by switching that to defaulting to .tar.gz. I had forgotten this fact, but yes, zip

Re: [Distutils] Deprecating little used file types/extensions on PyPI?

> On Aug 19, 2016, at 10:23 AM, Daniel Holth wrote: > > Consider that "setup.py sdist" produces .zip by default on Windows. This is an important consideration that nobody mentioned thus far— I have not used Windows to release a project to PyPI.. ever. So We should absolutely start by switchi

Re: [Distutils] Deprecating little used file types/extensions on PyPI?

The only issue I have with the proposal is the removal of .zip sdists because I would personally be inconvenienced by the removal of .zip. Consider that "setup.py sdist" produces .zip by default on Windows. On Fri, Aug 19, 2016 at 9:36 AM James Bennett wrote: > Every new configuration option add

Re: [Distutils] Deprecating little used file types/extensions on PyPI?

Every new configuration option added to a piece of software represents two opportunities: 1. An opportunity to introduce exciting new bugs. 2. An opportunity to introduce exciting new ways for users to click the thing that does the exact opposite of what they wanted to do. The proliferation of d

Re: [Distutils] Deprecating little used file types/extensions on PyPI?

> On Aug 19, 2016, at 8:46 AM, Daniel Holth wrote: > > Check out this Camden Bench. https://en.wikipedia.org/wiki/Camden_bench > . The creators of the bench > enumerated about 23 specific undesirable behaviors that they feel normal > benches allow

Re: [Distutils] Deprecating little used file types/extensions on PyPI?

Check out this Camden Bench. https://en.wikipedia.org/wiki/Camden_bench . The creators of the bench enumerated about 23 specific undesirable behaviors that they feel normal benches allow (like sleeping and skateboarding) and came up with a lump of concrete that you can sit on. On Fri, Aug 19, 2016

Re: [Distutils] Deprecating little used file types/extensions on PyPI?

> On Aug 19, 2016, at 2:53 AM, Nick Coghlan wrote: > > Unilaterally turning the feature off would be extraordinarily hostile > to current users - grace periods and sunset clauses are standard > features of change management processes for a reason, even when they > come at the cost of additional