Le Thu, 01 Aug 2013 17:03:03 +0200,
"Martin v. Löwis" a écrit :
> Am 30.07.13 23:32, schrieb Antoine Pitrou:
> > - it is held alive by a C extension: the main example is the locale
> > module, which is held alive by _io and in turn keeps alive other
> > Python modules (such as collections or r
Am 30.07.13 23:32, schrieb Antoine Pitrou:
> - it is held alive by a C extension: the main example is the locale
> module, which is held alive by _io and in turn keeps alive other
> Python modules (such as collections or re).
If the _locale module would use PEP 3121 (issue15662), this problem
On Wed, 31 Jul 2013 13:30:58 +1200
Greg Ewing wrote:
> Antoine Pitrou wrote:
> > - it is held alive through builtins: the site module patches builtins
> > with additional objects, which themselves keep references to the site
> > module's globals,
>
> The module probably *should* stay alive in
Antoine Pitrou wrote:
- it is held alive through builtins: the site module patches builtins
with additional objects, which themselves keep references to the site
module's globals,
The module probably *should* stay alive in that case, since
it's still accessible via those patched builtins.
On Tue, 30 Jul 2013 12:58:58 -0700
Guido van Rossum wrote:
> I'm very excited to see this happening! It's been a constant pain and
> one of the things I've always regretted. Thanks Antoine!
Note this is currently imperfect. I've identified two reasons why a
pure Python module could stay alive eve
I'm very excited to see this happening! It's been a constant pain and
one of the things I've always regretted. Thanks Antoine!
--Guido
On Tue, Jul 30, 2013 at 11:42 AM, Antoine Pitrou wrote:
>
> Hello,
>
> PEP 442 has now been committed in time for testing in Alpha 1.
>
> This paves the way for
