On behalf of the Python development community and the Python 3.4 release
team, I'm pleased to announce the availability of Python 3.4.4. Python
3.4.4 is the last version of Python 3.4.4 with binary installers, and
the end of "bugfix" support. After this release, Python 3.4.4 moves
into "sec
On Sun, Dec 20, 2015 at 7:25 PM, Alexander Belopolsky <
alexander.belopol...@gmail.com> wrote:
>
> On Sun, Dec 20, 2015 at 9:00 PM, Guido van Rossum
> wrote:
>
>> but I would really like to see a change in the repr of negative
>>> timedeltas:
>>>
>>> >>> timedelta(minutes=-1)
>>> datetime.timedel
[Tim]
>> But I wouldn't change repr() - the internal representation is fully
>> documented, and it's appropriate for repr() to reflect documented
>> internals as directly as possible.
[Alex]
> Note that in the case of float repr, the consideration of user convenience
> did win over "reflect docume
On Sun, Dec 20, 2015 at 10:25 PM, Tim Peters wrote:
> For
>
> >>> print(timedelta(minutes=-1))
>
> I'd like to see:
>
> -00:01:00
>
> But I wouldn't change repr() - the internal representation is fully
> documented, and it's appropriate for repr() to reflect documented
> internals as directly as
[Alexander Belopolsky]
>> ...
>> but I would really like to see a change in the repr of negative
>> timedeltas:
>>
>> >>> timedelta(minutes=-1)
>> datetime.timedelta(-1, 86340)
>>
>> And str() is not much better:
>>
>> >>> print(timedelta(minutes=-1))
>> -1 day, 23:59:00
>>
>> The above does not qu
On Sun, Dec 20, 2015 at 9:00 PM, Guido van Rossum wrote:
> but I would really like to see a change in the repr of negative timedeltas:
>>
>> >>> timedelta(minutes=-1)
>> datetime.timedelta(-1, 86340)
>>
>> And str() is not much better:
>>
>> >>> print(timedelta(minutes=-1))
>> -1 day, 23:59:00
>>
Guido van Rossum writes:
> (I was in a hurry and trying hard not to have to think :-).
That makes me feel much better! There *are* things that *aren't*
obvious, even to those born Dutch! :-)
Happy Holidays!
___
Python-Dev mailing list
Python-Dev@pyt
On Sun, Dec 20, 2015 at 5:00 PM, Alexander Belopolsky <
alexander.belopol...@gmail.com> wrote:
>
> On Sun, Dec 20, 2015 at 5:28 PM, Chris Angelico wrote:
>
>> > A helpful trivia: a year is approximately π times 10 million seconds.
>>
>> Sadly doesn't help here, as the timedelta for a number of ye
On Mon, Dec 21, 2015 at 12:00 PM, Alexander Belopolsky
wrote:
> On Sun, Dec 20, 2015 at 5:28 PM, Chris Angelico wrote:
>>
>> > A helpful trivia: a year is approximately π times 10 million seconds.
>>
>> Sadly doesn't help here, as the timedelta for a number of years looks like
>> this:
>>
>> >>>
From: gu...@python.org
Date: Sun, 20 Dec 2015 14:33:46 -0800
To: ros...@gmail.com
Subject: Re: [Python-Dev] Change the repr for datetime.timedelta (was Re:
Asynchronous context manager in a typical network server)
CC: python-dev@python.org
> I'm just curious on the backward compatibility impact.
Half-rhetorical half-genuine; you know better than me the history of breakage
due to such changes, anyway. I can't really think of anything you haven't, so
I'll just sit back.
From: gu...@python.org
Date: Sun, 20 Dec 2015 15:15:25 -0800
Subject: Re: [Python-Dev] Change the repr for datetime.time
On Sun, Dec 20, 2015 at 5:28 PM, Chris Angelico wrote:
> > A helpful trivia: a year is approximately π times 10 million seconds.
>
> Sadly doesn't help here, as the timedelta for a number of years looks like
> this:
>
> >>> datetime.timedelta(days=365*11)
> datetime.timedelta(4015)
>
>
The origin
On Sun, Dec 20, 2015 at 3:05 PM, Emanuel Barry wrote:
> From: gu...@python.org
>
> > I'm just curious on the backward compatibility impact.
>
> I'm just curious on the number of programs depending on the repr() of any
> object at all in production (not counting tests). I could be wrong, but it
>
On Sun, Dec 20, 2015 at 2:28 PM, Chris Angelico wrote:
> On Mon, Dec 21, 2015 at 9:02 AM, Alexander Belopolsky
> wrote:
> > On Fri, Dec 18, 2015 at 4:09 PM, Guido van Rossum
> wrote:
> >>>
> >>>
> >>> It's 11 days. Which is pretty reasonable server uptime.
> >>
> >>
> >> Oops, blame the repr()
On Mon, Dec 21, 2015 at 9:02 AM, Alexander Belopolsky
wrote:
> On Fri, Dec 18, 2015 at 4:09 PM, Guido van Rossum wrote:
>>>
>>>
>>> It's 11 days. Which is pretty reasonable server uptime.
>>
>>
>> Oops, blame the repr() of datetime.timedelta. I'm sorry I so rashly
>> thought I could do better tha
On Fri, Dec 18, 2015 at 4:09 PM, Guido van Rossum wrote:
>
>> It's 11 days. Which is pretty reasonable server uptime.
>>
>
> Oops, blame the repr() of datetime.timedelta. I'm sorry I so rashly
> thought I could do better than the OP.
>
A helpful trivia: a year is approximately π times 10 million
On 18.12.2015 22:09, Guido van Rossum wrote:
I guess we could make the default arg to sleep() 1e9. Or make it None
and special-case it. I don't feel strongly about this -- I'm not sure
how baffling it would be to accidentally leave out the delay and find
your code sleeps forever rather than rai
Just inform you that the deadline for the CfP of the PythonFOSDEM will
finish this evening.
If you have a last talk to submit, please do it.
Call For Proposals
==
This is the official call for sessions for the Python devroom at FOSDEM 2016.
FOSDEM is the Free and Open source So
18 matches
Mail list logo
