[Python-Dev] New relative import issue (original) (raw)
Guido van Rossum guido at python.org
Fri Sep 22 02:17:24 CEST 2006
- Previous message: [Python-Dev] New relative import issue
- Next message: [Python-Dev] New relative import issue
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 9/21/06, Greg Ewing <greg.ewing at canterbury.ac.nz> wrote:
Guido van Rossum wrote:
> Eek? If there are two third-party top-level packages A and B, by > different third parties, and A depends on B, how should A find B if > not via sys.path or something that is sufficiently equivalent as to > have the same problems? Some kind of configuration mechanism is needed, but I don't see why it can't be a static, declarative one rather than computed at run time.
That would preclude writing the code that interprets the static data in Python itself.
Despite the good use cases I think that's a big showstopper.
-- --Guido van Rossum (home page: http://www.python.org/~guido/)
- Previous message: [Python-Dev] New relative import issue
- Next message: [Python-Dev] New relative import issue
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]