what's the situation for Py3k? Should it always use absolute import there? On 3/10/07, Georg Brandl <g.brandl at gmx.net> wrote: > Currently, all C code that needs to import a module uses > PyImport_ImportModule which > (1) calls __builtin__.__import__ > (2) attempts relative imports > > Most of the time, though, at least (2) is wrong. > If we want to keep (1), PyImport_ImportModuleLevel can't be > used as a replacement. > So there should be a new API, called PyImport_ImportAbsolute > that gets a flag whether relative import should be allowed. > > Georg > > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: http://mail.python.org/mailman/options/python-dev/guido%40python.org > -- --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4