Re: [Python-Dev] PEP 489: Redesigning extension module loading

2015-03-18 Thread Nick Coghlan
On 18 March 2015 at 06:41, Mark Lawrence wrote: > On 16/03/2015 12:38, Petr Viktorin wrote: >> >> Hello, > > > Can you use anything from the meta issue http://bugs.python.org/issue15787 > for PEP 3121 and PEP 384 or will the work that you are doing render > everything done previously redundant? N

Re: [Python-Dev] PEP 489: Redesigning extension module loading

2015-03-17 Thread Mark Lawrence
On 16/03/2015 12:38, Petr Viktorin wrote: Hello, Can you use anything from the meta issue http://bugs.python.org/issue15787 for PEP 3121 and PEP 384 or will the work that you are doing render everything done previously redundant? -- My fellow Pythonistas, ask not what our language can do fo

Re: [Python-Dev] PEP 489: Redesigning extension module loading

2015-03-16 Thread Petr Viktorin
On Mon, Mar 16, 2015 at 4:42 PM, Jim J. Jewett wrote: > > On 16 March 2015 Petr Viktorin wrote: > >> If PyModuleCreate is not defined, PyModuleExec is expected to operate >> on any Python object for which attributes can be added by PyObject_GetAttr* >> and retrieved by PyObject_SetAttr*. > > I ass

Re: [Python-Dev] PEP 489: Redesigning extension module loading

2015-03-16 Thread Jim J. Jewett
On 16 March 2015 Petr Viktorin wrote: > If PyModuleCreate is not defined, PyModuleExec is expected to operate > on any Python object for which attributes can be added by PyObject_GetAttr* > and retrieved by PyObject_SetAttr*. I assume it is the other way around (add with Set and retrieve with Ge

[Python-Dev] PEP 489: Redesigning extension module loading

2015-03-16 Thread Petr Viktorin
Hello, On import-sig, I've agreed to continue Nick Coghlan's work on making extension modules act more like Python ones, work well with PEP 451 (ModuleSpec), and encourage proper subinterpreter and reloading support. Here is the resulting PEP. I don't have a patch yet, but I'm working on it.