On Mon, Oct 10, 2011 at 3:05 PM, Carl Meyer <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 ... > 2. People write code that imports things inconsistently (sometimes with > the project prefix, sometimes without it), and then when they go to > deploy (without manage.py or setup_environ), their imports break and > they don't understand why. This comes up frequently in #django. In order > to fix it they either have to make all their imports consistent, or add > both the inner and outer directories to sys.path/PYTHONPATH in their > deployment setup. Inconsistent imports should fail fast, not when you > move to production.
If anyone is interested in this specific problem, I've written a script to highlight places your sys.path allows aliasing of modules: https://gist.github.com/857091 -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
