Just drop support for 10.6 with Python 3.4. Problem solved. People on that
old of a version of the OS can build their own Python 3.4 or do the right
thing and upgrade or just install Linux.
This isn't Windows. Compiler tool chains are freely available for the
legacy platform. We don't need to main
On 17 September 2013 22:21, Guido van Rossum wrote:
> Congrats, I've accepted the PEP. Nice work! Please work with the reviewers
> on the issue on the code.
Good work, Steven!
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mai
On 18 September 2013 11:10, Philip Jenvey wrote:
>
> On Sep 16, 2013, at 1:05 PM, Antoine Pitrou wrote:
>
>> On Mon, 16 Sep 2013 15:48:54 -0400
>> Brett Cannon wrote:
So I would like to propose the following API change:
- Path.stat() (and stat-accessing methods such as get_mti
On Sep 16, 2013, at 1:05 PM, Antoine Pitrou wrote:
> On Mon, 16 Sep 2013 15:48:54 -0400
> Brett Cannon wrote:
>>>
>>> So I would like to propose the following API change:
>>>
>>> - Path.stat() (and stat-accessing methods such as get_mtime()...)
>>> returns an uncached stat object by default
>
On 18 Sep 2013 08:36, "Ethan Furman" wrote:
>
> On 09/17/2013 02:21 PM, Guido van Rossum wrote:
>>
>> Congrats, I've accepted the PEP. Nice work! Please work with the
reviewers on the issue on the code.
>
>
> Congratulations, Stephen!
Yay!
Cheers,
Nick.
>
> --
> ~Ethan~
>
>
benchmark.patch
Description: Binary data
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
On 09/17/2013 02:21 PM, Guido van Rossum wrote:
Congrats, I've accepted the PEP. Nice work! Please work with the reviewers on
the issue on the code.
Congratulations, Stephen!
--
~Ethan~
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.
On Tue, Sep 17, 2013 at 02:21:16PM -0700, Guido van Rossum wrote:
> Congrats, I've accepted the PEP. Nice work! Please work with the reviewers
> on the issue on the code.
Thank you, and thanks to everyone who contributed with the discussion.
> (Steven or Oscar, if either of you could work Oscar's
Congrats, I've accepted the PEP. Nice work! Please work with the reviewers
on the issue on the code.
(Steven or Oscar, if either of you could work Oscar's list of resolved
issues into a patch for the PEP I'll happily update it, just mail it to
p...@python.org.)
On Mon, Sep 16, 2013 at 5:06 PM, G
On Tue, 17 Sep 2013 15:39:25 -0400, Brett Cannon wrote:
> On Tue, Sep 17, 2013 at 2:45 PM, Glenn Linderman wrote:
> > On 9/17/2013 10:51 AM, Guido van Rossum wrote:
> >
> > But only the PSF has the list of original contributors and their licenses.
> >
> > So can that list be made public, and avai
On Tue, Sep 17, 2013 at 2:45 PM, Glenn Linderman wrote:
> On 9/17/2013 10:51 AM, Guido van Rossum wrote:
>
> But only the PSF has the list of original contributors and their licenses.
>
>
> So can that list be made public, and available in multiple archives?
>
Technically it already is public ba
On 9/17/2013 11:48 AM, MRAB wrote:
On 17/09/2013 16:37, Terry Reedy wrote:
On 2.7, >>> license() return a text that includes a complete list of
releases from 1.6 to 2.7 and stops there
Release Derived YearOwner GPL-
from
On 9/17/2013 10:51 AM, Guido van Rossum wrote:
But only the PSF has the list of original contributors and their
licenses.
So can that list be made public, and available in multiple archives?
___
Python-Dev mailing list
Python-Dev@python.org
https://m
On Tue, 17 Sep 2013 12:38:31 -0400, Donald Stufft wrote:
> On Sep 17, 2013, at 12:25 PM, "R. David Murray" wrote:
> > I don't think this PEP changes the inclusion calculus, because I don't
> > think we've given any real weight to that in stdlib inclusion decisions.
> > I think the decision making
On Tue, 17 Sep 2013 09:47:48 -0700
Guido van Rossum wrote:
>
> IIRC this table was added when a few core Python developers including
> myself left CNRI in 2000. We had a bit of an argument about the license
> (not too much though -- in the end things came out alright). Some lawyer at
> CNRI thoug
On Tue, Sep 17, 2013 at 10:39 AM, Antoine Pitrou wrote:
> On Tue, 17 Sep 2013 09:47:48 -0700
> Guido van Rossum wrote:
> >
> > IIRC this table was added when a few core Python developers including
> > myself left CNRI in 2000. We had a bit of an argument about the license
> > (not too much though
On Tue, Sep 17, 2013 at 8:47 AM, Antoine Pitrou wrote:
> Le Tue, 17 Sep 2013 11:37:48 -0400,
> Terry Reedy a écrit :
>
> > On 2.7, >>> license() return a text that includes a complete list of
> > releases from 1.6 to 2.7 and stops there
> > Release Derived YearOwner
> I don't really understand why the releases should be manually listed.
> Is it some kind of defensive coding?
I think it's to give people who care about such things all the
information they need to make informed decisions. As I recall, the 1.6
series was problematic, because it wasn't actually op
On Sep 17, 2013, at 12:25 PM, "R. David Murray" wrote:
> This PEP looks great to me. Thanks to everyone involved.
>
> On Wed, 18 Sep 2013 00:46:01 +1000, Nick Coghlan wrote:
>> Reducing the burden of actually installing a third-party package should
>> also decrease the pressure to add every u
This PEP looks great to me. Thanks to everyone involved.
On Wed, 18 Sep 2013 00:46:01 +1000, Nick Coghlan wrote:
> Reducing the burden of actually installing a third-party package should
> also decrease the pressure to add every useful module to the standard
> library. This will allow additions
Le Tue, 17 Sep 2013 11:37:48 -0400,
Terry Reedy a écrit :
> On 2.7, >>> license() return a text that includes a complete list of
> releases from 1.6 to 2.7 and stops there
> Release Derived YearOwner GPL-
> fromc
On 17/09/2013 16:37, Terry Reedy wrote:
On 2.7, >>> license() return a text that includes a complete list of
releases from 1.6 to 2.7 and stops there
Release Derived YearOwner GPL-
fromcompatible? (1)
0.9
On 2.7, >>> license() return a text that includes a complete list of
releases from 1.6 to 2.7 and stops there
Release Derived YearOwner GPL-
fromcompatible? (1)
0.9.0 thru 1.2 1991-1995 CWI
After a couple of rounds of review on distutils-sig, and with Martin
agreeing to serve as BDFL-Delegate, it's time for the pip
bootstrapping proposal to run the gauntlet of python-dev :)
The last round of review showed that there were a few things we were
assuming people knew (based on the many, m
2013/9/17 Victor Stinner :
> Issue tracking the implementation:
> http://bugs.python.org/issue18874
If you want to test the implementation, you can try the following repository:
http://hg.python.org/features/tracemalloc
Or try the patch attached on the issue #18874 on the Python default
version.
25 matches
Mail list logo
