crmoreo.blogg.se

1. #Cannot use import statement outside a module how to
2. #Cannot use import statement outside a module code

Which puts the package directory on sys.path and leads to this double Layout gets into trouble by running manage.py from inside a package, Using the -m switch from the parent directory in order to ensure that While I’m using an embedded test case as an example here, similar issuesĪrise any time you execute a script directly from inside a package without If I need to work in a differentĭirectory for some reason, well, that’s why I also like to have multiple Programming in Python - leave my working directory set to the projectĭirectory, and then use the -m switch to execute relevant submodules This last approach is actually how I prefer to use my shell when # working directory: project python - m example.

#Cannot use import statement outside a module how to

Know how to do) or else to make sure to import the module instead of Something novice, or even many veteran, Python programmers are going to Setup was to either set it manually in test_foo.py itself (hardly “example” to be a top level package will still break though).įor a long time, the only way to get sys.path right with this kind of Intra-package references, the last two commands shown may actually workįor Python 3.3 and later versions. That if the project exclusively uses explicit relative imports for Python’s import system works, but also with how it gets initialised. Quite likely to break if you try them, and the error messages won’t makeĪny sense if you’re not already intimately familiar not only with the way That’s right, that long list is of all the methods of invocation that are test_foo python - c "from _foo import main main()" py python project / example / tests / test_foo. test_foo python - c "from tests.test_foo import main main()" # working directory: project example / tests / test_foo. py python - m test_foo python - c "from test_foo import main main()" # working directory: project/example tests / test_foo.

#Cannot use import statement outside a module code

# These commands will most likely *FAIL* due to problems with the way # the import state gets initialised, even if the test code is correct # working directory: project/example/tests. Tests inside package directories like this, and prefer a parallel hierarchy,īut I favour the ability to use explicit relative imports to keep module Layouts along these lines in my own projects - a lot of people hate nesting The command line by filename rather than using the -m switch.Ĭonsider a project & package layout like the following (I typically use package Happens automatically if you attempt to run a module inside a package from Unfortunately, this is still a really easy guideline to violate, as it With the site name, as described in the release notes).

In version 1.4 (site-specific apps now always need to be fully qualified State, so this behaviour was eliminated from the default project layout Is a recipe for confusion if there is any meaningful mutable module level Namespace, and these are actually two different copies of the module. Up exactly this situation for site-specific applications - the applicationĮnds up being accessible as both app and site.app in the module Package (if the higher level directory containing the package itself isĪs an example, Django (up to and including version 1.3) used to be guilty of setting (since the directory is on sys.path) and as a submodule of the Now potentially accessible under two different names: as a top level module The reason this is problematic is that every module in that directory is This next trap exists in all current versions of Python, including 3.3, andĬan be summed up in the following general guideline: “Never add a packageĭirectory, or any directory inside a package, directly to the Python path”. Requests for clarification can be posted on BitBucket. The explanations with version details before 2.6.Īs with all my essays on this site, suggestions for improvement or Of it applies to earlier versions as well, but I won’t be qualifying any of This essay only officially covers Python versions back to Python 2.6. On mailing lists and Q&A sites like Stack Overflow. Import system, there are quite a few common missteps that come up regularly Various backwards compatibility issues that can cause strange behaviour,Īnd may need to be understood in order to figure out how some third partyįurthermore, even without invoking any of the more exotic features of the Sys.path is initialised are still somewhat challenging to figure out.Įven though 3.3 cleaned up a lot of things, it still has to deal with Import semantics, and even following the release of 3.3, the details of how Release of Python 3.3, there was no comprehensive explanation of the expected Python’s import system is powerful, but also quite complicated. Traps for the Unwary in Python’s Import System ¶