#18028 closed Bug (invalid)
manage.py startapp creates apps in "wrong" path
| Reported by: | Aviral Dasgupta | Owned by: | Aviral Dasgupta |
|---|---|---|---|
| Component: | Core (Management commands) | Version: | 1.4 |
| Severity: | Normal | Keywords: | |
| Cc: | Aviral Dasgupta | Triage Stage: | Unreviewed |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | yes | UI/UX: | no |
Description
Historically (before Django 1.4), manage.py startapp created apps in the project directory (since it was inside it), but now, apps are created alongside the project directory unless you specifically indicate otherwise. Since the standard organisation of Django projects places apps inside projects, manage.py should create new apps inside the project directory, as was the case before
Change History (3)
comment:1 by , 13 years ago
| Owner: | changed from to |
|---|
comment:2 by , 13 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:3 by , 13 years ago
Oh, sorry, about that. You're right, it's now the new layout. My bad.
Version 0, edited 13 years ago by (next)
Note:
See TracTickets
for help on using tickets.
There isn't really a concept of "project directory"; a Django project is just a bunch of Python packages.
This change is intentional, and the new layout matches the recommended best practices. Please see the release notes for more information.