GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • [ date ]
  • [ thread ]
  • [ subject ]
  • [ author ]

This view

  • Original page
  • New address

GeezerVison is showing mail.python.org — [Python-Dev] PEP 489: module m_traverse called with NULL module state

[Python-Dev] PEP 489: module m_traverse called with NULL module state

Antoine Pitrou solipsis at pitrou.net
Tue Dec 19 10:19:26 EST 2017

  • Previous message (by thread): [Python-Dev] PEP 489: module m_traverse called with NULL module state
  • Next message (by thread): [Python-Dev] PEP 489: module m_traverse called with NULL module state
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Tue, 19 Dec 2017 16:10:06 +0100
Petr Viktorin <encukou at gmail.com> wrote:
> >
> > Speaking of which, the doc is not very clear: is PEP 489 required for
> > multi-interpreter support or is PyModule_GetState() sufficient?  
> 
> Yes, it is possible to have proper subinterpreter support without
> multi-phase init.

Thanks.  I guess the C API docs need a user-friendly section laying out
the various methods for initializing a module, and their various
advantages :-)

Regards

Antoine.

  • Previous message (by thread): [Python-Dev] PEP 489: module m_traverse called with NULL module state
  • Next message (by thread): [Python-Dev] PEP 489: module m_traverse called with NULL module state
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the Python-Dev mailing list
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.