Message77467
| Author |
brett.cannon |
| Recipients |
amaury.forgeotdarc, blakemadden, brett.cannon |
| Date |
2008年12月09日.22:36:32 |
| SpamBayes Score |
1.6739217e-05 |
| Marked as misclassified |
No |
| Message-id |
<bbaeab100812091436w3503c9f7kd17818ef1e2d61ea@mail.gmail.com> |
| In-reply-to |
<1228862059.71.0.531690540242.issue4612@psf.upfronthosting.co.za> |
| Content |
On Tue, Dec 9, 2008 at 14:34, Amaury Forgeot d'Arc
<report@bugs.python.org> wrote:
>
> Amaury Forgeot d'Arc <amauryfa@gmail.com> added the comment:
>
> When python is embedded in a program, there must be a way for the
> program to export
> some of its functions to python - a module that resides in the main
> executable.
>
> You cannot use the import machinery to import such a module, because
> there is no
> separate file to find and load. Instead, the embedding program
> explicitly calls the
> module init() function.
> With python 2.x, this creates the module *and* inserts it into
> sys.modules. Then
> subsequent imports will find it directly in sys.modules.
>
> mod_python for example works this way.
> I maintain that the sample is still valid, and should be made to work
> somehow.
That's what I mean; the example is off as in incorrect. Not off as in
trying to do something silly. |
|