I just created a branch for the ssize_t changes I had been working on
for a while. I hope to follow up with a PEP quickly.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Armin Rigo wrote:
No, I know about this. I meant -- obviously, I'd have expected... --
precisely the sequence of commands that my example shows:
I still managed to miss that point :-( My fault, you are right.
Regards,
Martin
___
Python-Dev mailing
Michael Hudson wrote:
For a different approach, would it be possible to have
a subversion trigger put the revision number into some file in the
repository?
Not easily, to my knowledge. Assuming that the export will be made
from a tag, the revision at which the tag was created (along with
the
On Fri, 2005-12-16 at 17:11 -0500, Phillip J. Eby wrote:
It looks like using 'svnversion -c . | cut -f2 -d:' would get the
most-recent committed version, plus the letter M if there are local
changes. That sounds like what we should be using.
That way, a build with local revisions would
Barry Warsaw wrote:
AFAICT, the reason to use -c is so that changes outside the Python
source tree (i.e. in the sandbox) won't show up in Python's build
number. That's fine although I wouldn't mind leaving off the -c since
you'll still get the same snapshot of code from a revisioned checkout
Here's the summary for the first half of November -- sorry for the bit
of a delay. As always, let me or Tony know if you have any
corrections!
=
Summary Announcements
=
--
Reminder: Python is now on Subversion!
On Sat, 2005-12-17 at 23:48 +0100, Martin v. Löwis wrote:
Barry Warsaw wrote:
AFAICT, the reason to use -c is so that changes outside the Python
source tree (i.e. in the sandbox) won't show up in Python's build
number. That's fine although I wouldn't mind leaving off the -c since
you'll
On 11/21/05, Fredrik Lundh [EMAIL PROTECTED] wrote:
Neal Norwitz wrote:
I just checked in the modification below. I'm not sure if this
behaviour is on purpose or by accident.
[ /f shows diff on linux and windows ]
I checked in a fix for this so float('0x3') should not work on any platform
I'm not sure where the problem is, but this code leaks a reference:
parser = ET.XMLParser() ; parser.feed('xtext/x')
You need this to set it up:
from xmlcore.etree import cElementTree as ET
This isn't a memory leak according to valgrind.
Also, I noticed several places where errors where
