-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
| Guido> I recall seeing this too, though my memory is fuzzy. I believe
| Guido> there's a temp file or directory left behind from a
previous run
| Guido> that you need to delete.
|
| Thanks. I zapped my build dire
I've done my own profiling with a different script. I was able to verify
Andrews results. The pymalloc approach makes int creation slightly
slower and has almost no effect on floats.
The creation of 1000 times a list of 1000 ints (range(1000)) is about
20msec slower. It almost doubles the time for
Andrew MacIntyre wrote:
> I tried a LIFO stack implementation (though I won't claim to have done it
> well), and found it slightly slower than no freelist at all. The
> advantage of such an approach is that the known size of the stack makes
> deallocating excess objects easy (and thus no need for
>
After the success of January's bug day, which closed 37 issues, let's
have another one this month! Here's the brief announcement:
Python Bug Day: Saturday, February 23 2008. Meet in the #python-dev
IRC channel on irc.freenode.net and help improve Python. For more
information, see http://wiki.py
Guido> I recall seeing this too, though my memory is fuzzy. I believe
Guido> there's a temp file or directory left behind from a previous run
Guido> that you need to delete.
Thanks. I zapped my build directory then reran
configure ;; make ;; make test
Seems to be working bette
I recall seeing this too, though my memory is fuzzy. I believe there's
a temp file or directory left behind from a previous run that you need
to delete. Maybe the source around that error will give you a hint on
what its name is. I know I eventually got over is.
On Feb 10, 2008 11:34 AM, <[EMAIL
I'm having trouble with test_bsddb on my new MacBook Pro (OS X 10.5.1).
Many tests give this error:
Traceback (most recent call last):
File "/Users/skip/src/python/trunk/Lib/test/test_bsddb.py", line 18, in
setUp
self.f = self.openmethod[0](self.fname, self.openflag, cachesize=3
> This has been fixed on the trunk in response to issue 2021, but I'm not
> sure of the current status of the 2.5 maintenance branch. Should I wait
> until after 2.5.2 is released before backporting? Or backport it now?
Please backport it now. The code freeze for the 2.5 branch will come
Wednesd
Assuming the fix isn't going to break other things, I'd say now is the
time, unless Martin says otherwise. Waiting until after 2.5.2 doesn't
make a lot of sense -- either it is a backportable fix, or it isn't.
If it is backportable, it can go in as long as the 2.5.2 code freeze
isn't in effect.
On
In 2.5, tempfile.NamedTemporaryFile passes requests for __enter__ and
__exit__ through to the underlying file object, which ends up breaking
in a couple of different ways (by a fortuitous coincidence, it actually
works in most respects on Windows, so tempfile.TemporaryFile will mostly
do the ri
10 matches
Mail list logo
