Permalink
Browse files

Clarified Python namespace collisions, as the error message might dif…

…fer now
  • Loading branch information...
1 parent 183179a commit a1d377b1d66435d102ae8ad02fb7124e115a8ef7 @fwenzel fwenzel committed Jul 22, 2011
Showing with 6 additions and 10 deletions.
  1. +6 −10 troubleshooting.rst
View
16 troubleshooting.rst
@@ -2,21 +2,17 @@
Troubleshooting
===============
-"Could not import settings"
+Python namespace collisions
---------------------------
-Example::
+When naming your top-level project (i.e., the directory you're checking
+your code out into), keep in mind that this will **become a Python module**,
+so name it accordingly.
- Error: Could not import settings 'code.settings_local' (Is it on
- sys.path?): No module named settings_local
-
-This is caused by namespace problems in Python's sys path.
-
-Make sure that your project directory is called differently than:
+Make sure that your project directory is called **differently than**:
* any Python builtin (``code``, ``email``, ...)
-* any module on your Python path (such as ``testapp``, which is used by
- django-nose)
+* any module on your Python path (such as ``nose``, ``celery``, ``redis``)
* any app inside your ``apps`` directory (such as ``commons``, which is
used by playdoh).

0 comments on commit a1d377b

Please sign in to comment.