[Python-Dev] Ann: PyPy Sprint before PYCON 2005 in Washington

2005-02-14 Thread Christian Tismer
PyPy Sprint before PYCON 2005 in Washington --- In the four days from 19th March till 22th March (inclusive) the PyPy team will host a sprint on their new Python-in-Python implementation. The PyPy project was granted funding by the European Union as part of

[Python-Dev] Re: [Zope] Windows Low Fragementation Heap yields speedup of ~15%

2005-02-14 Thread Tim Peters
[Gfeller Martin] > I'm running a large Zope application on a 1x1GHz CPU 1GB mem > Window XP Prof machine using Zope 2.7.3 and Py 2.3.4 > The application typically builds large lists by appending > and extending them. That's historically been an especially bad case for Windows systems, although the

Re: [Python-Dev] builtin_id() returns negative numbers

2005-02-14 Thread Josiah Carlson
James Y Knight <[EMAIL PROTECTED]> wrote: > > > On Feb 14, 2005, at 10:41 AM, Tim Peters wrote: > > >> Wouldn't it be more elegant to make builtin_id() return an unsigned > >> long integer? > > > > I think so. This is the function ZODB 3.3 uses, BTW: > > > > def positive_id(obj): > > """Re

Re: [Python-Dev] builtin_id() returns negative numbers

2005-02-14 Thread Tim Peters
[James Y Knight] > I think it'd be nice to change it, too. Twisted also uses a similar > function. > > However, last time this topic came up, this Tim Peters guy argued > against it. ;) > > Quoting > http://mail.python.org/pipermail/python-dev/2004-November/050049.html: > >> Python doesn't promise

Re: [Python-Dev] builtin_id() returns negative numbers

2005-02-14 Thread James Y Knight
On Feb 14, 2005, at 10:41 AM, Tim Peters wrote: Wouldn't it be more elegant to make builtin_id() return an unsigned long integer? I think so. This is the function ZODB 3.3 uses, BTW: def positive_id(obj): """Return id(obj) as a non-negative integer.""" [...] I think it'd be nice to change it,

Re: [Python-Dev] builtin_id() returns negative numbers

2005-02-14 Thread Tim Peters
[Troels Walsted Hansen] > The Python binding in libxml2 uses the following code for __repr__(): > > class xmlNode(xmlCore): > def __init__(self, _obj=None): > self._o = None > xmlCore.__init__(self, _obj=_obj) > > def __repr__(self): > return "" % (self.name, id (se

[Python-Dev] builtin_id() returns negative numbers

2005-02-14 Thread Troels Walsted Hansen
Hi all, The Python binding in libxml2 uses the following code for __repr__(): class xmlNode(xmlCore): def __init__(self, _obj=None): self._o = None xmlCore.__init__(self, _obj=_obj) def __repr__(self): return "" % (self.name, id (self)) With Python 2.3.4 I'm seeing w

[Python-Dev] Re: [Python-checkins] python/dist/src/Doc/lib libimp.tex, 1.36, 1.36.2.1 libsite.tex, 1.26, 1.26.4.1 libtempfile.tex, 1.22, 1.22.4.1 libos.tex, 1.146.2.1, 1.146.2.2

2005-02-14 Thread Just van Rossum
[EMAIL PROTECTED] wrote: > \begin{datadesc}{PY_RESOURCE} > -The module was found as a Macintosh resource. This value can only be > -returned on a Macintosh. > +The module was found as a Mac OS 9 resource. This value can only be > +returned on a Mac OS 9 or earlier Macintosh. > \end{datadesc}