When I said it wasn't decided I was totally serious. No decision has
been reached.
However, I strongly recommend that you try to write all your code
using PyUnicode and PyBytes, avoiding PyString completely. Even if
str8/PyString will remain in existence, it will be a last resort type
for backward
On 8/13/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> It's official! The second annual Python Sprint @ Google is happening
> again: August 22-25 (Wed-Sat).
I can't attend this year (damn doctor's appt.), but I will try to be
on Google Talk (username of bcannon) in case I can help out somehow
r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I maintain the sqlite module in the standard library, which makes heavy use
of PyString_* C API. Now I've made it work under Python 3000 insofar as
tests pass, but the new Python string semantics mean I have more work to do
here and make some API choic
On 8/13/07, Russell E Owen <[EMAIL PROTECTED]> wrote:
> In article <[EMAIL PROTECTED]>,
> "Stephen J. Turnbull" <[EMAIL PROTECTED]> wrote:
>
> > Guido van Rossum writes:
> >
> > > However, the old universal newlines feature also set an attibute named
> > > 'newlines' on the file object to a tupl
In article <[EMAIL PROTECTED]>,
"Stephen J. Turnbull" <[EMAIL PROTECTED]> wrote:
> Guido van Rossum writes:
>
> > However, the old universal newlines feature also set an attibute named
> > 'newlines' on the file object to a tuple of up to three elements
> > giving the actual line endings that
Martin v. Löwis wrote:
> I'd like to remove support for Windows 9x (95, 98(SE), ME)
> soon from the Python trunk. This would primarily affect all
> wide-string APIs (which would be considered present
> unconditionally), as well as certain "new" Win32 functions;
> in this cleanup, I would also drop
It's official! The second annual Python Sprint @ Google is happening
again: August 22-25 (Wed-Sat). We're sprinting at two locations, this
time Google headquarters in Mountain View and the Google office in
Chicago (thanks to Brian Fitzpatrick). We'll connect the two sprints
with full-screen videoc
Paul> ... that files can have *either* bare \n, *or* the combination
Paul> \r\n, to delimit lines.
As someone else pointed out, \r needs to be supported as well. Many Mac
applications (Excel comes to mind) still emit text files with \r as the line
terminator.
Skip
_
