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

2016-08-28 Thread Sylvain Corlay
Hi All, The beta deadline for new features is approaching dangerously. I agree with Thomas that being able to require Python 3.6 for a project does not appear so distant for me (as soon as it is a Python 3 project only). Any chance to get this through? Checking support for language features

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

2016-08-24 Thread Ralf Gommers
On Mon, Aug 22, 2016 at 6:50 PM, Thomas Kluyver wrote: > On Mon, Aug 22, 2016, at 07:15 AM, Sylvain Corlay wrote: > > I find this worrying that the main arguments to not include a patch would > be that > > - this part of the standard library is not very maintained (things

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

2016-08-24 Thread Sylvain Corlay
Hi, Any feedback on this? Sylvain On Mon, Aug 22, 2016 at 10:25 AM, Sylvain Corlay wrote: > I think that Thomas' proposal makes sense. > > I would be ok to also add it to setuptools so that it can be used sooner > by projects that don't require python 3.6. > >

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

2016-08-22 Thread Sylvain Corlay
ritium-list= > sdamon@python.org] *On Behalf Of *Sylvain Corlay > *Sent:* Monday, August 22, 2016 2:16 AM > *To:* Ralf Gommers <ralf.gomm...@gmail.com> > *Cc:* distutils-sig <distutils-sig@python.org> > *Subject:* Re: [Distutils] Proposed new Distutils API for compiler f

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

2016-08-22 Thread tritium-list
] On Behalf Of Sylvain Corlay Sent: Monday, August 22, 2016 2:16 AM To: Ralf Gommers <ralf.gomm...@gmail.com> Cc: distutils-sig <distutils-sig@python.org> Subject: Re: [Distutils] Proposed new Distutils API for compiler flag detection (Issue26689) Hi, On Sun, Aug 21, 2016 at 10:31 PM,

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

2016-08-22 Thread Thomas Kluyver
On Mon, Aug 22, 2016, at 07:15 AM, Sylvain Corlay wrote: > I find this worrying that the main arguments to not include a patch > would be that > > - this part of the standard library is not very maintained (things >don't get merged) > - earlier versions of won't have it Would it make sense

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

2016-08-22 Thread Sylvain Corlay
Hi, On Sun, Aug 21, 2016 at 10:31 PM, Ralf Gommers wrote: > > On top of that there are technical reasons (don't want to test > combinations of python + setuptools that both change per release) and > organizational ones (distutils maintenance is terrible, many simple

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

2016-08-21 Thread Ralf Gommers
On Mon, Aug 22, 2016 at 6:10 AM, Donald Stufft wrote: > We’re reaching a point where *some* projects are announcing the end of > Python 2 support as of a certain date, but let us not forget that Python > 2.7 is still an order of magnitude more than any other version of Python

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

2016-08-21 Thread Donald Stufft
We’re reaching a point where *some* projects are announcing the end of Python 2 support as of a certain date, but let us not forget that Python 2.7 is still an order of magnitude more than any other version of Python in terms of downloads from PyPI. > On Aug 21, 2016, at 2:08 PM, Sylvain

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

2016-08-21 Thread Sylvain Corlay
Although we are reaching a tipping point where a lot of projects are announcing the end of Python 2 support as of a certain date. Whatever is in the latest version of Python 3 when it will be considered a sane decision to have a Python 3-only library will be considered standard. On Sun, Aug 21,

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

2016-08-21 Thread Donald Stufft
> On Aug 21, 2016, at 5:18 AM, Sylvain Corlay wrote: > > With this reasoning, nothing should ever be added to the standard library. Packaging is a bit different than other things because the network effect is much more prominent. There’s no real way to say, install

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

2016-08-21 Thread Sylvain Corlay
On Sun, Aug 21, 2016 at 8:40 AM, Nathaniel Smith wrote: > > Having the `has_flag` in a different location from `has_function` would > be weird in my opinion. > > I think the point though is that in your proposal, has_flag is in > distutils 3.6, but has_function is in distutils

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

2016-08-21 Thread Nathaniel Smith
On Aug 20, 2016 3:09 PM, "Sylvain Corlay" wrote: > > Hi Ralf, > > On Sat, Aug 20, 2016 at 11:42 PM, Ralf Gommers wrote: >>> >>> >>> On python-dev and in the bug tracker, Sylvain has understandably asked for a review with an eye to adding this new

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

2016-08-20 Thread Sylvain Corlay
Hi Ralf, On Sat, Aug 20, 2016 at 11:42 PM, Ralf Gommers wrote: > >> On python-dev and in the bug tracker, Sylvain has understandably asked >> for a review with an eye to adding this new feature to Python 3.6 whose >> feature code cutoff is scheduled for a few weeks from

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

2016-08-20 Thread Ralf Gommers
On Sat, Aug 20, 2016 at 8:33 AM, Ned Deily wrote: > 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

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

2016-08-19 Thread Ned Deily
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) >