On Fri, Jun 7, 2013 at 5:16 PM, Łukasz Langa wrote:
> On 7 cze 2013, at 22:50, PJ Eby wrote:
>
>> On Fri, Jun 7, 2013 at 10:27 AM, Thomas Wouters wrote:
>>> This isn't a new bug, but it's exposed by always importing weakref and
>>> atexit during interpreter startup. I'm wondering if that's reall
On 7 cze 2013, at 22:50, PJ Eby wrote:
> On Fri, Jun 7, 2013 at 10:27 AM, Thomas Wouters wrote:
>> This isn't a new bug, but it's exposed by always importing weakref and
>> atexit during interpreter startup. I'm wondering if that's really necessary
>> :)
>
> In short, the overall answer right n
On Fri, Jun 7, 2013 at 10:27 AM, Thomas Wouters wrote:
> This isn't a new bug, but it's exposed by always importing weakref and
> atexit during interpreter startup. I'm wondering if that's really necessary
> :)
Importing it during startup isn't necessary per se; imports needed
only by the generic
On 7 cze 2013, at 16:27, Thomas Wouters wrote:
>
> On Wed, Jun 5, 2013 at 3:20 AM, lukasz.langa
> wrote:
> +from weakref import WeakKeyDictionary
>
> This isn't a new bug, but it's exposed by always importing weakref and atexit
> during interpreter startup. I'm wondering if that's really ne
On Fri, Jun 7, 2013 at 10:27 AM, Thomas Wouters wrote:
>
> On Wed, Jun 5, 2013 at 3:20 AM, lukasz.langa
> wrote:
>
>> +from weakref import WeakKeyDictionary
>>
>
> FYI, this change exposes a bug in the atexit module involving
> subinterpreters, causing the refleaks reported by Antoine's daily re
On Wed, Jun 5, 2013 at 3:20 AM, lukasz.langa wrote:
> +from weakref import WeakKeyDictionary
>
FYI, this change exposes a bug in the atexit module involving
subinterpreters, causing the refleaks reported by Antoine's daily report:
interpreter startup now always imports weakref, which imports atex
Dnia 5 cze 2013 o godz. 16:31 Brett Cannon napisał(a):
> Any chance you could move your definitions for "generic function" and "single
> dispatch" to the glossary and just link to them here?
Sure thing.
--
Ł
___
Python-Dev mailing list
Python-Dev@py
