Hi all!
If you wonder about the lack of progress reports on pep-431, this is
because of a lack of progress. I simply haven't had any time to work
on this. I considered make a kickstarter so I could take time off from
working, but to be honest, even with that, I still have no time to
realistically
That's a shame, but there's always 3.5 and we'll hopefully have an
easier path to pip install pytz in 3.4 (once I get PEP 453 revised
appropriately).
Cheers,
Nick.
On 2 October 2013 22:17, Lennart Regebro rege...@gmail.com wrote:
Hi all!
If you wonder about the lack of progress reports on
On Wed, Oct 2, 2013 at 2:17 PM, Lennart Regebro rege...@gmail.com wrote:
If you wonder about the lack of progress reports on pep-431, this is
because of a lack of progress. I simply haven't had any time to work
on this. I considered make a kickstarter so I could take time off from
working, but
On Wed, Oct 2, 2013 at 3:05 PM, Dirkjan Ochtman dirk...@ochtman.nl wrote:
On Wed, Oct 2, 2013 at 2:17 PM, Lennart Regebro rege...@gmail.com wrote:
If you wonder about the lack of progress reports on pep-431, this is
because of a lack of progress. I simply haven't had any time to work
on this.
Am 30.09.13 20:11, schrieb Antoine Pitrou:
On Mon, 30 Sep 2013 16:18:57 +0200 (CEST)
martin.v.loewis python-check...@python.org wrote:
http://hg.python.org/cpython/rev/c1a294bbb4fa
changeset: 85882:c1a294bbb4fa
branch: 2.7
parent: 85877:dd55d54b2a15
user:Martin v. Löwis
That could be a possibility as well.
On Wed, Oct 2, 2013 at 6:14 PM, Stuart Bishop stu...@stuartbishop.net wrote:
On Wed, Oct 2, 2013 at 9:42 PM, Lennart Regebro rege...@gmail.com wrote:
On Wed, Oct 2, 2013 at 3:05 PM, Dirkjan Ochtman dirk...@ochtman.nl wrote:
On Wed, Oct 2, 2013 at 2:17 PM,
On Wed, 2 Oct 2013 18:16:48 +0200 (CEST)
serhiy.storchaka python-check...@python.org wrote:
http://hg.python.org/cpython/rev/d48ac94e365f
changeset: 85931:d48ac94e365f
user:Serhiy Storchaka storch...@gmail.com
date:Wed Oct 02 19:15:54 2013 +0300
summary:
Use cached
Hi,
I'm looking back on a rather unpleasant experience that I recently had in
this developer community. Actually, twice by now. Here's what I take from it:
You should take responsibility for your commits.
Sounds like a simple thing - in theory. People make mistakes, that's
normal. You can't
On 10/2/13 1:31 PM, Antoine Pitrou wrote:
On Wed, 2 Oct 2013 18:16:48 +0200 (CEST)
serhiy.storchaka python-check...@python.org wrote:
http://hg.python.org/cpython/rev/d48ac94e365f
changeset: 85931:d48ac94e365f
user:Serhiy Storchaka storch...@gmail.com
date:Wed Oct 02 19:15:54
02.10.13 20:31, Antoine Pitrou написав(ла):
On Wed, 2 Oct 2013 18:16:48 +0200 (CEST)
serhiy.storchaka python-check...@python.org wrote:
http://hg.python.org/cpython/rev/d48ac94e365f
changeset: 85931:d48ac94e365f
user:Serhiy Storchaka storch...@gmail.com
date:Wed Oct 02
I don't remember where, but I remember that I also saw things like
str=str, len=len, So you keep the same name, but you use fast
local lookups instead of slow builtin lookups.
Victor
2013/10/2 Antoine Pitrou solip...@pitrou.net:
On Wed, 2 Oct 2013 18:16:48 +0200 (CEST)
serhiy.storchaka
On Wed, Oct 2, 2013 at 2:58 PM, Stefan Behnel stefan...@behnel.de wrote:
Hi,
I'm looking back on a rather unpleasant experience that I recently had in
this developer community. Actually, twice by now. Here's what I take from
it:
You should take responsibility for your commits.
Sounds
On Wed, Oct 2, 2013 at 9:42 PM, Lennart Regebro rege...@gmail.com wrote:
On Wed, Oct 2, 2013 at 3:05 PM, Dirkjan Ochtman dirk...@ochtman.nl wrote:
On Wed, Oct 2, 2013 at 2:17 PM, Lennart Regebro rege...@gmail.com wrote:
If you wonder about the lack of progress reports on pep-431, this is
Stefan,
You blew up a minor design disagreement over the new async parsing API for
XML into a huge impending disaster that would destroy the XML library APIs
forever. In truth, even if we had left the original commit alone it would,
at worst, have resulted in a slightly inconsistent API design.
On 3 Oct 2013 09:00, Nick Coghlan ncogh...@gmail.com wrote:
Stefan,
You blew up a minor design disagreement over the new async parsing API
for XML into a huge impending disaster that would destroy the XML library
APIs forever. In truth, even if we had left the original commit alone it
would,
Stefan Behnel writes:
Hi, I'm looking back on a rather unpleasant experience that I
recently had in this developer community. Actually, twice by
now. Here's what I take from it: You should take responsibility for
your commits.
I have no clue who you're addressing this advice to. If it's
16 matches
Mail list logo
