Closed jean closed 8 years ago
That is very strange. I cannot reproduce this (import doesn't fail in ipython; using python2.7 and 3.5). I am testing in virtualenv, in Linux, but my thinking usually was that python can do 'import X' when X.py is in current directory.
Yes, that's what I expect too. I'll check some more.
J On 14 Jul 2016 11:53 am, "Michael Egorov" notifications@github.com wrote:
That is very strange. I cannot reproduce this (import doesn't fail in ipython; using python2.7 and 3.5). I am testing in virtualenv, in Linux, but my thinking usually was that python can do 'import X' when X.py is in current directory.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/zerodb/zerodb/pull/45#issuecomment-232556191, or mute the thread https://github.com/notifications/unsubscribe/AAFLQNuZyk99IwHsAKqFRPHSYVjPWI7fks5qVcCsgaJpZM4JMFAL .
@michwill the sys.path
issue only shows up when trying to execute the example while in the zerodb-manage console
. I've updated the PR.
Assuming I'm in the
demo
directory, unless I append '.' to my path, import fails.This feels rather hacky, is there a better way?