A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2006-September/068859.html below:

[Python-Dev] New relative import issue

[Python-Dev] New relative import issue [Python-Dev] New relative import issueGreg Ewing greg.ewing at canterbury.ac.nz
Wed Sep 20 02:06:41 CEST 2006
Steve Holden wrote:

> This does, of course, assume that you're importing modules from the 
> filestore, which assumption is no longer valid in the presence of PEP 
> 302 importers.

Well, you need to allow for a sufficiently abstract
notion of "filesystem".

I haven't really thought it through in detail. It
just seems as though it would be a lot less confusing
if you could figure out from static information which
module will get imported by a given import statement,
instead of having it depend on the history of run-time
modifications to sys.path. One such kind of static
information is the layout of the filesystem.

--
Greg
More information about the Python-Dev mailing list

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