FYI, I've uploaded a patch that provides for cross-compilation on Windows
between 32 and 64 bit platforms - all comments invited!
Thanks,
Mark
-Original Message-
From: Mark Hammond [mailto:[EMAIL PROTECTED]
Sent: Sunday, 30 March 2008 6:01 PM
To: [EMAIL PROTECTED]
Subject: [issue2513]
2008/3/30, Martin v. Löwis [EMAIL PROTECTED]:
If you'd like, I can merge the rest.
If you have the time to figure it all out, sure.
I found that quite a tedious task, and had to spent
on some patches quite a long time to figure out what
they do, and what the 3.x equivalent should be.
Facundo Batista schrieb:
Me for myself, I thought that the trunk - 3k merge was easier!
Sometimes I commited changes to the trunk, don't worrying about 3k at
all, thinking it was a mostly automatic process.
Now that I know this, I will start patching both trunk 3k simultaneously...
In
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 30, 2008, at 3:35 AM, Martin v. Löwis wrote:
Likewise, if you are accessing the repository over bzr+ssh, in
general,
you can just ssh to the machine, and do a regular ls. In the specific
2008/3/31, Christian Heimes [EMAIL PROTECTED]:
In most cases it's easy. Usually it takes me less than 20 minutes per
day to merge the chances from trunk - py3k. In this particular case
several obstacles come together. The changes in the AST and parser code
aren't trivial, I'm not familiar
Hello,
It seems this subject has had quite a bit of history. Tim Peters demonstrated
the problem in 2003 in this message:
http://mail.python.org/pipermail/python-dev/2003-June/036537.html
In short, Python file objects release the GIL before calling any C stdlib
function on their embedded FILE
test_io is the only leaky test on trunk that I know of. I narrowed
down the leaks to the code below.
It's possible there are other leaks in test_io.
n
--
import sys, gc
import _fileio, io
class FileIO(_fileio._FileIO, io.RawIOBase):
def close(self):
io.RawIOBase.close(self)
def
