[Python-Dev] Summary of Tracker Issues

2008-01-18 Thread Tracker
ACTIVITY SUMMARY (01/11/08 - 01/18/08) Tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue number. Do NOT respond to this message. 1329 open (+31) / 11986 closed (+15) / 13315 total (+46) Open issues with patches: 437 Average durati

Re: [Python-Dev] What to do for bytes in 2.6?

2008-01-18 Thread Christian Heimes
Christian Heimes wrote: > Ah, you like to keep it simple. The aliases are easily to implement. > Give me twenty minutes to implement it and write some unit tests. http://bugs.python.org/issue1865 ___ Python-Dev mailing list Python-Dev@python.org http://

Re: [Python-Dev] What to do for bytes in 2.6?

2008-01-18 Thread Facundo Batista
2008/1/18, Guido van Rossum <[EMAIL PROTECTED]>: > I don't think any of that is necessary. I would rather have the > following two in the language by default (see my response to Terry and > Raymond): > > bytes is an alias for str (not even a subclass) > b"" is an alias for "" +1 -- .Facundo

Re: [Python-Dev] What to do for bytes in 2.6?

2008-01-18 Thread Christian Heimes
Guido van Rossum wrote: > I don't think any of that is necessary. I would rather have the > following two in the language by default (see my response to Terry and > Raymond): > > bytes is an alias for str (not even a subclass) > b"" is an alias for "" Ah, you like to keep it simple. The aliases a

Re: [Python-Dev] What to do for bytes in 2.6?

2008-01-18 Thread Guido van Rossum
On Jan 18, 2008 12:27 AM, Christian Heimes <[EMAIL PROTECTED]> wrote: > Guido van Rossum wrote: > > Oh, you won't. Just don't use the -3 command-line flag and don't put > > "from __future__ import " at the top of your modules, and > > you won't have to change your ways at all. You can continue to >

Re: [Python-Dev] What to do for bytes in 2.6?

2008-01-18 Thread Guido van Rossum
On Jan 17, 2008 11:24 PM, Thomas Heller <[EMAIL PROTECTED]> wrote: > Is the bytes type required for PEP3118 'Revising the buffer protocol'? I don't think so. I would like to see this PEP backported (but keep the old 'buffer' of course for b/w compatibility). Whenever this PEP talks about bytes we

Re: [Python-Dev] What to do for bytes in 2.6?

2008-01-18 Thread Guido van Rossum
On Jan 17, 2008 9:30 PM, Terry Reedy <[EMAIL PROTECTED]> wrote: > "Guido van Rossum" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > | Is it reading text or binary data from stream blah? We can't tell. If > | it's meant to be reading text, 2to3 should leave it alone. But if it's >

Re: [Python-Dev] PEP 370, open questions

2008-01-18 Thread Christian Heimes
Suraj Barkale wrote: > Can this be changed into using %APPDATA% by default and changing to > %HOMEDRIVE%%HOMEPATH% based on some MSI switch? I'll stick to APPDATA but I'm going to introduce a new env var PYTHONUSERBASE. It overwrites the path to the base directory and allows users (and companies)

Re: [Python-Dev] PEP 370, open questions

2008-01-18 Thread Antoine Pitrou
Christian Heimes cheimes.de> writes: > > I assume ~/.local was first introduced by the freedesktop.org people. On > my box it's only used for some desktop related apps like > ~/.local/share/Trash or XFC4. Same here, only ~/.local/share is used (on two boxes, one Mandriva and one Ubuntu).

Re: [Python-Dev] building _ctypes in trunk fails first time around

2008-01-18 Thread Christian Heimes
Guido van Rossum wrote: > If I run "make clean" and then "make", builting _ctypes fails with this > message: > > *** WARNING: renaming "_ctypes" since importing it failed: No module > named _weakref > > Typing "make" a second time fixes this -- it seems a simple matter of > _ctypes being built b

Re: [Python-Dev] What to do for bytes in 2.6?

2008-01-18 Thread Christian Heimes
Guido van Rossum wrote: > Oh, you won't. Just don't use the -3 command-line flag and don't put > "from __future__ import " at the top of your modules, and > you won't have to change your ways at all. You can continue to > distribute your packages in 2.5 syntax that will also work with 2.6, > and yo

[Python-Dev] Error in PEP3118?

2008-01-18 Thread Thomas Heller
Hi Travis, The pep contains this sample: """ Nested array :: struct { int ival; double data[16*4]; } """i:ival: (16,4)d:data: """ """ I think it is wrong and must be changed to the following; is this correct? """ Nested