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 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 projects. Thanks, Sylvain On Thu, Aug 25, 2016 at 6:41 AM, Ralf Gommers <ralf.gomm...@gmail.com> wrote: > > On Mon, Aug 22, 2016 at 6:50 PM, Thomas Kluyver <tho...@kluyver.me.uk> > wrote: > >> 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. > > Ralf > > >> 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. >> >> Thomas >> >
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
