On Mon, Jan 26, 2009 at 2:00 PM, Guido van Rossum wrote:
> On Mon, Jan 26, 2009 at 1:57 PM, Giovanni Bajo wrote:
>> On Mon, 26 Jan 2009 10:31:55 -0800, Guido van Rossum wrote:
>>
>>> On Mon, Jan 26, 2009 at 8:08 AM, Paul Hummer
>>> wrote:
At a previous employer, we had this same discussion
On Wed, Dec 28, 2011 at 5:37 PM, Jesse Noller wrote:
>
>
> On Wednesday, December 28, 2011 at 8:28 PM, Michael Foord wrote:
>
>> Hello all,
>>
>> A paper (well, presentation) has been published highlighting security
>> problems with the hashing algorithm (exploiting collisions) in many
>> progra
On Wed, Feb 1, 2012 at 5:03 PM, Victor Stinner
wrote:
> datetime.datetime
> -
>
> datetime.datetime only supports microsecond resolution, but can be enhanced
> to support nanosecond.
>
> datetime.datetime has issues:
>
> - there is no easy way to convert it into "seconds since the
On Fri, Feb 3, 2012 at 3:57 AM, Victor Stinner
wrote:
>> datetime.datetime
>>
>> - as noted earlier in the thread, total_seconds() actually gives you a
>> decent timestamp value and always returning UTC avoids timezone issues
>
> os.stat() and time.time() use the local time.
The documentation dis
On Thu, Feb 2, 2012 at 4:59 PM, Nick Coghlan wrote:
> datetime.datetime
>
> - real problem with the idea is that not all timestamps can be easily
> made absolute (e.g. some APIs may return "time since system started"
> or "time since process started")
I think this is an argument for returning the
On Fri, Feb 3, 2012 at 11:17 AM, Antoine Pitrou wrote:
> On Fri, 3 Feb 2012 11:04:14 -0800
> Jeffrey Yasskin wrote:
>> On Thu, Feb 2, 2012 at 4:59 PM, Nick Coghlan wrote:
>> > datetime.datetime
>> >
>> > - real problem with the idea is that not all time
On Tue, Mar 13, 2012 at 5:03 PM, Michael Foord
wrote:
>
> On 13 Mar 2012, at 16:57, Victor Stinner wrote:
>
>> Hi,
>>
>> I added two functions to the time module in Python 3.3: wallclock()
>> and monotonic(). I'm unable to explain the difference between these
>> two functions, even if I wrote them
On Tue, Mar 13, 2012 at 6:10 PM, Nadeem Vawda wrote:
> On Wed, Mar 14, 2012 at 3:03 AM, Victor Stinner
> wrote:
>> I suppose that most libraries and programs will have to implement a
>> similar fallback.
>>
>> We may merge both functions with a flag to be able to disable the
>> fallback. Example:
On Fri, Mar 23, 2012 at 4:25 PM, Victor Stinner
wrote:
> Hi,
>
> time.steady(strict=True) looks to be confusing for most people, some
> of them don't understand the purpose of the flag and others don't like
> a flag changing the behaviour of the function.
>
> I propose to replace time.steady(stric
FWIW, I'm not sure you're the right person to drive time PEPs. You
don't seem to have come into it with much knowledge of time, and it's
taken several repetitions for you to take corrections into account in
both this discussion and the Decimal/datetime representation PEP.
On Mon, Mar 26, 2012 at 4
On Tue, Jul 17, 2012 at 3:20 PM, Victor Stinner
wrote:
>> It's the JIT compiler of Unladen Swallow that "failed"; in
>> my understanding because LLVM is crap (i.e. it is slow, memory-consuming,
>> and buggy) - as a low-level virtual machine; it may be ok as a compiler
>> backend (but I still think
101 - 111 of 111 matches
Mail list logo
