Browse Source

Issue #12484: Remove a mention of Py_InitModule() and _PyImport_FixupExtension().

Thanks to Alejandro Santos for the bug report and Anish Shah for the
patch.
pull/9921/head
Brett Cannon 10 years ago
parent
commit
762d5ea875
  1. 5
      Doc/c-api/import.rst
  2. 14
      Doc/faq/extending.rst
  3. 1
      Misc/ACKS

5
Doc/c-api/import.rst

@ -236,11 +236,6 @@ Importing Modules
For internal use only.
.. c:function:: PyObject* _PyImport_FixupExtension(char *, char *)
For internal use only.
.. c:function:: int PyImport_ImportFrozenModuleObject(PyObject *name)
Load a frozen module named *name*. Return ``1`` for success, ``0`` if the

14
Doc/faq/extending.rst

@ -247,20 +247,6 @@ For Red Hat, install the python-devel RPM to get the necessary files.
For Debian, run ``apt-get install python-dev``.
What does "SystemError: _PyImport_FixupExtension: module yourmodule not loaded" mean?
-------------------------------------------------------------------------------------
This means that you have created an extension module named "yourmodule", but
your module init function does not initialize with that name.
Every module init function will have a line similar to::
module = Py_InitModule("yourmodule", yourmodule_functions);
If the string passed to this function is not the same name as your extension
module, the :exc:`SystemError` exception will be raised.
How do I tell "incomplete input" from "invalid input"?
------------------------------------------------------

1
Misc/ACKS

@ -1310,6 +1310,7 @@ Pete Sevander
Denis Severson
Ian Seyer
Dmitry Shachnev
Anish Shah
Daniel Shahaf
Mark Shannon
Ha Shao

Loading…
Cancel
Save