ACTIVITY SUMMARY (08/05/07 - 08/12/07)
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.
1295 open ( +8) / 11130 closed ( +2) / 12425 total (+10)
Average duration of open issues: 690 days.
Medi
On Aug 11, 2007, at 10:29 AM, Guido van Rossum wrote:
>> Is this ok: when newline='\r\n' or newline='\r' is passed, only that
>> string is used to determine
>> the end of lines. No translation to '\n' is done.
>
> I *think* it would be more useful if it always returned lines ending
> in \n (not \r
On 8/11/07, Tony Lownds <[EMAIL PROTECTED]> wrote:
>
> On Aug 10, 2007, at 11:23 AM, Guido van Rossum wrote:
>
> > Python 3.0 currently has limited universal newlines support: by
> > default, \r\n is translated into \n for text files, but this can be
> > controlled by the newline= keyword parameter
On Aug 10, 2007, at 11:23 AM, Guido van Rossum wrote:
> Python 3.0 currently has limited universal newlines support: by
> default, \r\n is translated into \n for text files, but this can be
> controlled by the newline= keyword parameter. For details on how, see
> PEP 3116. The PEP prescribes that
Can somebody please review this patch:
https://sourceforge.net/support/tracker.php?aid=1692335
It aims to fix the pickling of exceptions whose __init__ methods don't call
Exception.__init__ at all, or with a different number of arguments.
This should be fixed before 2.5.2.
Georg
--
Thus spake
