Refs #15372 -- Removed obsolete docs about manage.py setting sys.path. #10954
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current django-admin documentation page contains an outdated and incorrect description of what manage.py does.
The docs say that manage.py adds the project package to
sys.path
, but this is not true as of Django 1.4.In versions of Django before 1.4, the manage.py script invoked logic that would add your project to
sys.path
. This code lived indjango.core.management.setup_environ
.The changes to manage.py and the deprecation of this sys.path behavior were documented in the 1.4 release notes. It looks like the logic was removed in 1.6.