upgrading python django project 1.3 to 1.5

Question

currently i have python project using django version 1.3 running on mountain lion OS and now i want to upgrade it to django 1.5. But when i put it and try to do python manage.py runserver i get an error saying

Error: Can't find the file 'settings.py' in the directory containing 'manage.py'. It appears you've customized things. You'll have to run django-admin.py, passing it your settings module. (If the file settings.py does indeed exist, it's causing an ImportError somehow.)

i realized that the project structure is different, is there any way to convert or upgrading the 1.3 project into 1.5 project somehow?

score 6 · Accepted Answer · answered Jun 04 '13 at 09:46

6

Every Django release has release note with upgrading instructions.

Unfortunately the process is not automated, so you'll have to carefully go through both documents.

answered Jun 04 '13 at 09:46

kirelagin

13,248
2
42
57

The specific error OP is getting should not appear in Django 1.5. Release notes say: *"(The old-style manage.py will continue to work as before until Django 1.6. In 1.5 it will raise DeprecationWarning)."* – gertvdijk Jun 04 '13 at 15:40
@gertvdijk That's what I though too. But, actually, the question was about upgrading, not fixing the error. Anyway, during the upgrade process the OP fill have to restructure his project and. most likely, the error will go away. – kirelagin Jun 04 '13 at 15:43
@gertvdijk By the way, my guess is that he has already modified the project structure (i.e. moved `settings.py`) but hasn't updated `manage.py`. – kirelagin Jun 04 '13 at 15:44

score 1 · Answer 2 · answered Jun 04 '13 at 10:01

To elaborate on what kirelagin mentioned, the project structure and layout has changed in 1.4 so you need to reflect that in your setup. You can see the notes on this in the release documentation:

Django 1.4 ships with an updated default project layout and manage.py file for the startproject management command. These fix some issues with the previous manage.py handling of Python import paths that caused double imports, trouble moving from development to deployment, and other difficult-to-debug path issues.

This will mean there is a conflict in where Django expects your settings.py to be.

upgrading python django project 1.3 to 1.5

2 Answers2

Linked