> On Windows x64, sizeof(size_t) > sizeof(long), so the
> existing PyLong_FromSsize_t and PyLong_FromSize_t
> implementations in longobject.c are just plain wrong.
There are a whole bunch of other areas where longobject.c could do with casts
to silence Windows x64 compiler warnings (where it's s
2008/4/13, Greg Ewing <[EMAIL PROTECTED]>:
> I'm not sure what to do about that, though. Maybe some
> sort of locale setting that makes repr() of a string not
> escape chars that fall into some kind of "normal" set
> according to the user's native language?
>
Here's my idea.
repr() cannot con
On Windows x64, sizeof(size_t) > sizeof(long), so the existing
PyLong_FromSsize_t and PyLong_FromSize_t implementations in longobject.c are
just plain wrong. I've patched it as follows, but as I'm not well versed in
the many intricacies of longobject.c, I'd appreciate input from others.
As fa
On Sat, Apr 12, 2008 at 5:17 PM, Greg Ewing <[EMAIL PROTECTED]> wrote:
> Guido van Rossum wrote:
> > We'd
> > need a third form (eek!) that would preserve the string quotes but be
> > more lenient about non-ASCII. Personally, I think some custom loop to
> > print the values is good enough.
>
>
I thought I had a reasonable proposal: deprecate in 3.1, remove in
3.3. Adding a PendingDeprecationWarning in 3.0 would be fine. Doing
anything in 2.6 would not be fine, except perhaps making it a
PendingDeprecationWarning whan -3 is given.
On Sat, Apr 12, 2008 at 11:05 PM, Nick Coghlan <[EMAIL PR
On Mon, Apr 14, 2008 at 2:05 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> I thought I had a reasonable proposal: deprecate in 3.1, remove in
> 3.3. Adding a PendingDeprecationWarning in 3.0 would be fine. Doing
> anything in 2.6 would not be fine, except perhaps making it a
> PendingDepreca
On Mon, Apr 14, 2008 at 6:02 AM, Trent Nelson <[EMAIL PROTECTED]> wrote:
>
> On Windows x64, sizeof(size_t) > sizeof(long), so the existing
> PyLong_FromSsize_t and PyLong_FromSize_t implementations in longobject.c are
> just plain wrong. I've patched it as follows, but as I'm not well versed in
> > On Mon, Apr 14, 2008 at 6:02 AM, Trent Nelson <[EMAIL PROTECTED]> wrote:
> >
> > On Windows x64, sizeof(size_t) > sizeof(long), so the existing
> > PyLong_FromSsize_t and PyLong_FromSize_t implementations in longobject.c
> > are just plain wrong. I've patched it as follows, but as I'm not well
On Mon, Apr 14, 2008 at 8:01 PM, Trent Nelson <[EMAIL PROTECTED]> wrote:
>
> Yeah, that's the 'wrong' part I was referring to. I guess I wanted to
> bring that issue up as well as question the actual implementation. For
> example, if we fixed the if statement, we'd having something looking like:
Guido van Rossum wrote:
> A complaint about this would carry more weight when it came from
> someone who actually has to deal with the issue
It's not a complaint, just something I thought of. If
Japanese programmers aren't actually bothered by this,
then I'm not either.
> Another issue is that r
This is a repeat of a question that came up on the "Decimal(unicode)" thread
a
little while ago. I think it needs an answer, so I'm reposting it in its
own thread.
I couldn't find any other previous discussion of this; apologies if I'm
rehashing
old issues.
Currently, int() and float() accept byt
2008/4/15, Greg Ewing <[EMAIL PROTECTED]>:
> Guido van Rossum wrote:
>
> > A complaint about this would carry more weight when it came from
> > someone who actually has to deal with the issue
>
>
> It's not a complaint, just something I thought of. If
> Japanese programmers aren't actually bothe
2008/4/14, Michael Urman <[EMAIL PROTECTED]>:
> This theory sounds good to me. Should it perhaps also convert Unicode
> whitespace and control characters (categories Z* and C*)? While these
> will often still be printable, like \n and \t they may not be
> distinguishable from some number of ASC
On Mon, Apr 14, 2008 at 8:04 PM, atsuo ishimoto <[EMAIL PROTECTED]> wrote:
> 2008/4/14, Michael Urman <[EMAIL PROTECTED]>:
>
> > This theory sounds good to me. Should it perhaps also convert Unicode
> > whitespace and control characters (categories Z* and C*)? While these
> > will often still
On Sun, Apr 13, 2008 at 6:48 AM, Haoyu Bai <[EMAIL PROTECTED]> wrote:
> Gregory P. Smith wrote:
> > -cc: python-dev
> > +cc: python-3000
>
> Thanks for Gregory to point out my mistake and forward this mail to
> python-3000. I really feel sorry for my mistake.
Don't worry about it.
> I have a
> Philosophically, this seems wrong
I agree.
Regards,
Martin
___
Python-3000 mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe:
http://mail.python.org/mailman/options/python-3000/archive%40mail-archive
> Shall I check in a fix?
Be my guest (I take it you'll address the original
PyLong_FromSsize_t/FromSize_t issue that I posted a patch for, right?).
Trent.
From: Mark Dickinson [mailto:[EMAIL PROTECTED]
Sent: 15 April 2008 01:30
17 matches
Mail list logo
