[Distutils] Proposed new Distutils API for compiler flag detection (Issue26689)
sylvain.corlay at gmail.com
Sun Aug 28 06:34:17 EDT 2016
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
Any chance to get this through? Checking support for language features will
be more and more required since new version of the C++ standard are
becoming more frequent. I understand that it is not an issue for a project
like numpy, but this is a check I do in every single one of my extension
On Thu, Aug 25, 2016 at 6:41 AM, Ralf Gommers <ralf.gommers at gmail.com>
> On Mon, Aug 22, 2016 at 6:50 PM, Thomas Kluyver <thomas at kluyver.me.uk>
>> There's obviously some cost in code duplication; I haven't looked at the
>> code in question, so I don't know how bad this is.
> This patch is pretty short and understandable, so not bad.
>> I've run into this argument before when trying to change things in
>> non-packaging-related parts of the stdlib, and I agree with Sylvain that
>> it's fundamentally problematic. If we're trying to improve the stdlib,
>> we're obviously taking a long view, but that's how we ensure the stdlib is
>> still useful in a few years time. This goes for packaging tools as much as
>> anything else.
> This I don't agree with - packaging is fundamentally different for the
> reasons Donald gave.
>> I already have projects where I'm happy to require Python >=3.4, so being
>> able to depend on Python 3.6 is not such a distant prospect.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Distutils-SIG