On Sat, 07 May 2011 23:16:51 +0200
raymond.hettinger wrote:
>
> +class TestErrorHandling_Python(unittest.TestCase):
> +module = py_heapq
This class contains no tests.
Regards
Antoine.
___
Python-Dev mailing list
Python-Dev@python.org
http://ma
On 2011-05-07, at 03:39 , Glyph Lefkowitz wrote:
>
> I don't know if there's a programming language and runtime with a real-time,
> VM-cooperating garbage collector that actually exists today which has all the
> bells and whistles required to implement an OS kernel, so I wouldn't give the
> Lin
Hi,
Le 06/05/2011 22:07, R. David Murray a écrit :
On Fri, 06 May 2011 19:51:31 +0200, =?UTF-8?Q?=C3=89ric_Araujo?=
wrote:
regrtest helpfully reports when a test leaves the environment
unclean
(sys.path, os.environ, logging._handlerList), but I think the
implementation is buggy: it compares o
Le 06/05/2011 20:57, Vinay Sajip a écrit :
Éric Araujo netwok.org> writes:
Second: in packaging, we have two modules that create a logging
handler. I’m not sure how if we should change the code or fix the
tests
to restore the _handlerList, or how.
If you are saying this happens in your
I wanted to take a few minutes to let you all know that the recent call for
help with translating Python Insider was met with a wave of enthusiastic
contributors. We now have teams prepared to translate all posts to Simplified
and Traditional Chinese, German, Japanese, Portuguese, Romanian, and
On Fri, 6 May 2011 21:39:10 -0400
Glyph Lefkowitz wrote:
>
> The assertion that "modern hardware" is not designed for big data-structure
> pointer-chasing is also a bit silly. On the contrary, modern hardware has
> evolved staggeringly massive caches, specifically because large programs
> (wh
Stefan Behnel wrote:
It's a dead-end that is referenced by a cycle, that's all.
But shouldn't it be breaking the cycle by clearing one
of the objects that's actually part of the cycle, rather
than part of the dead-end?
I can't see how the Document could get picked for clearing
unless it was a
Greg Ewing, 07.05.2011 02:26:
Stefan Behnel wrote:
After all, the described crash case indicates that the Document
destructor was called before all of the Element destructors had been
called, although all Elements reference their Document, but the Document
does not refer to any of the Elements,
