MRAB wrote:
Maybe, also, strptime could support "%*f" to gobble as many digits as
are available.
The * would suggest that the number of digits is being
supplied as a parameter. Maybe "%?f".
--
Greg
___
Python-Dev mailing list
Python-Dev@python.org
ht
2014-12-11 15:47 GMT+01:00 Giampaolo Rodola' :
> I still think the only *real* obstacle remains the lack of important
> packages such as twisted, gevent and pika which haven't been ported yet.
twisted core works on python 3, right now. Contribute to Twisted if
you want to port more code... Or star
2014-12-11 22:00 GMT+01:00 MRAB :
>
> On 2014-12-11 18:33, Skip Montanaro wrote:
>>
>>
>> there are likely to be situations where the caller assumes it
>> generates a six-digit string. I did a little poking around. It seems
>> like "%N" isn't used.
>>
>> Could the number of digits be specified? Yo
On 2014-12-11 18:33, Skip Montanaro wrote:
On Thu, Dec 11, 2014 at 11:58 AM, Matthieu Bec wrote:
...or keep using "%f" if acceptable...
That might be a problem. While it will probably work most of the time,
there are likely to be situations where the caller assumes it
generates a six-digit st
On Thu Dec 11 2014 at 3:14:42 PM Dan Stromberg wrote:
> On Thu, Dec 11, 2014 at 11:35 AM, Mark Roberts wrote:
> > I disagree. I know there's a huge focus on The Big Libraries (and
> wholesale
> > migration is all but impossible without them), but the long tail of
> > libraries is still incredibl
Ethan Furman :
> On 12/11/2014 11:14 AM, Guido van Rossum wrote:
>> (I wouldn't be surprised if there wasn't -- while computer clocks
>> have a precision in nanoseconds, that doesn't mean they are that
>> *accurate* at all (even with ntpd running).
>
> The real-world use cases deal with getting th
On Thu, Dec 11, 2014 at 11:35 AM, Mark Roberts wrote:
> I disagree. I know there's a huge focus on The Big Libraries (and wholesale
> migration is all but impossible without them), but the long tail of
> libraries is still incredibly important. It's like saying that migrating the
> top 10 Perl lib
On Thu, 11 Dec 2014 13:43:05 -0600
Skip Montanaro wrote:
> On Thu, Dec 11, 2014 at 1:23 PM, Antoine Pitrou wrote:
> > I think strftime / strptime support is a low-priority concern on this
> > topic, and can probably be discussed independently of the core
> > nanosecond support.
>
> Might be low-
On Thu, Dec 11, 2014 at 1:23 PM, Antoine Pitrou wrote:
> I think strftime / strptime support is a low-priority concern on this
> topic, and can probably be discussed independently of the core
> nanosecond support.
Might be low-priority, but with %f support as a template, supporting
something to s
On 12/11/2014 11:14 AM, Guido van Rossum wrote:
>
> (I wouldn't be surprised if there wasn't -- while computer clocks have a
> precision in
> nanoseconds, that doesn't mean they are that *accurate* at all (even with
> ntpd running).
[reading issue]
The real-world use cases deal with getting thi
On 12/11/2014 11:23 AM, Antoine Pitrou wrote:
>
> I think strftime / strptime support is a low-priority concern on this
> topic, and can probably be discussed independently of the core
> nanosecond support.
Agreed.
--
~Ethan~
signature.asc
Description: OpenPGP digital signature
__
I disagree. I know there's a huge focus on The Big Libraries (and wholesale
migration is all but impossible without them), but the long tail of
libraries is still incredibly important. It's like saying that migrating
the top 10 Perl libraries to Perl 6 would allow people to completely ignore
all of
I think strftime / strptime support is a low-priority concern on this
topic, and can probably be discussed independently of the core
nanosecond support.
Regards
Antoine.
On Thu, 11 Dec 2014 11:14:27 -0800
Guido van Rossum wrote:
> Another issue to consider here is that parsing and printing sh
Another issue to consider here is that parsing and printing should be
symmetrical. The %f format gobbles up exactly 6 digits.
Finally, strptime and strftime are not invented by Python, the same
functions with (mostly) the same format characters are defined by other
languages. Is there not a single
On Thu, Dec 11, 2014 at 11:58 AM, Matthieu Bec wrote:
> ...or keep using "%f" if acceptable...
That might be a problem. While it will probably work most of the time,
there are likely to be situations where the caller assumes it
generates a six-digit string. I did a little poking around. It seems
Thanks Stephen elaborating on the process.
and apologies, I was dismissing the last point only half jokingly.
I read the comment for strftime / strptime in the report as meant to
remember to implement it. It seems picking a new format letter (or keep
using "%f" if acceptable) that would accept
Just adapt your current PEP.
On Thu Dec 11 2014 at 10:02:23 AM Donald Stufft wrote:
>
> On Dec 11, 2014, at 9:59 AM, Brett Cannon wrote:
>
> As I didn't hear any objections, I'm officially stating that I expect
> initial draft PEPs to be in by February 1 to know who is in the running to
> focus
> On Dec 11, 2014, at 9:59 AM, Brett Cannon wrote:
>
> As I didn't hear any objections, I'm officially stating that I expect initial
> draft PEPs to be in by February 1 to know who is in the running to focus
> discussion. I then expect complete PEPs by April 1 so I can read them before
> PyCo
As I didn't hear any objections, I'm officially stating that I expect
initial draft PEPs to be in by February 1 to know who is in the running to
focus discussion. I then expect complete PEPs by April 1 so I can read them
before PyCon and have informed discussions while I'm there. I will then
plan t
On Wed, Dec 10, 2014 at 5:59 PM, Bruno Cauet wrote:
> Hi all,
> Last year a survey was conducted on python 2 and 3 usage.
> Here is the 2014 edition, slightly updated (from 9 to 11 questions).
> It should not take you more than 1 minute to fill. I would be pleased if
> you took that time.
>
> Her
20 matches
Mail list logo
