manage.py not finding custom commands when run from different directory (or through a symlink in a different directory)

[icyhandofcrap]

​http://code.djangoproject.com/ticket/5825

Similar to the above case, but manage.py will not find custom commands if called through a symlink from a different directory or from a different directory other than the project directory.

[icyhandofcrap]

The attached patch attempts to resolve the path of manage.py if it is a symbolic link, and also gets the parent directory of manage.py, not relying on getcwd()

[Alex Gaynor]

This path uses the Python2.5 ternary conditional syntax, please write this in a way that is 2.3 compatible.

[icyhandofcrap]

okay changed.

[anonymous]

I'm not sure how I would do unit tests for this, but this is a demo of the code. Make symbolic links, run it from different directories, etc. and it will print out the parent directory of the script itself. Of course, doesn't work with hard links.

[Ulrich Petri]

I can't reproduce the problem (Mac OS 10.5, Python 2.5, Django trunk r10697)

[anonymous]

Well the issue is if under installed apps, you have:

'myproject.app',

instead of

'app'.

Then when you run manage.py from a different directory, manage.py doesn't detect that it is in the myproject directory already and fails to import app. Then it doesn't import the custom commands.

[Eric Holscher]

If that is the case, I think we can punt this to 1.2 with a "don't do this". We were talking about documenting that you should always import your apps with the full path at the sprints in Prague.

[Jacob]

Yes, you should always use absolute paths for INSTALLED_APPS, and everywhere else, too. This is really just another incarnation of the "project" abstracting being confusing and hurting users later on; in this case, a basic understanding of PYTHONPATH explains what's going on here.

[Jacob]

Milestone 1.1 deleted