Author iankko
Recipients akr, barry, benjamin.peterson, glyph, gregory.p.smith, iankko, loewis, pitrou, psss, thoger
Date 2009-07-15.20:54:52
SpamBayes Score 1.52431e-06
Marked as misclassified No
Message-id <1247691294.69.0.129101013522.issue5753@psf.upfronthosting.co.za>
In-reply-to
Content
Link to older Python tracker issue discussing the same problem and
closed with "won't fix":

    http://bugs.python.org/issue946373

Strange enough, but implied from reading above issue, just an
idea (don't shoot :)). Wouldn't it be possible to recognize,
if the module name the script | embedded application is trying
to load belongs to && conflicts with the 'standard' Python module
names as listed in:

  http://docs.python.org/modindex.html

and in that case:
  a, issue a warning by loading it?
  b, refuse to import it, in case it doesn't come from usual
     standard Python modules location?

Probably off-topic, but is there in Python some mechanism how to
determine, if the module / module name belongs to:
  a, 'standard Python module set' or
  b, is a custom module, written by Python user?
     (via the Python's interpreter __main__ module's namespace
      dictionary? -- based on [1])

[1] http://www.linuxjournal.com/article/8497
History
Date User Action Args
2009-07-15 20:54:55iankkosetrecipients: + iankko, loewis, barry, gregory.p.smith, pitrou, benjamin.peterson, glyph, psss, akr, thoger
2009-07-15 20:54:54iankkosetmessageid: <1247691294.69.0.129101013522.issue5753@psf.upfronthosting.co.za>
2009-07-15 20:54:53iankkolinkissue5753 messages
2009-07-15 20:54:52iankkocreate