Support for Django 1.4

Issue #1399 resolved
Hynek Cernoch
created an issue

I am preparing fixes to Satchmo for Django 1.4

= South = Due to dependency on South, clonesatchmo.py currently writes warnings "RuntimeWarning: DateTimeField received a naive datetime (2012-03-...) while time zone support is active." With the stable South 0.7.3.

The South issue http://south.aeracode.org/ticket/1012 related also to time zones is the blocking issue why South 0.7.4 can not be released yet.

I temporarely change the installation source from stable to development until 0.7.4 is released. (it solves our problem)

Comments (2)

  1. Hynek Cernoch reporter

    (It is not Satchmo issue in effect.)

    Database simple/simple.db reports a small problem with Django 1.4 for manage.py syncdb with disabled South

    Syncing...
    Creating tables ...
    The following content types are stale and need to be deleted:
    
        auth | message
    
    Any objects related to these content types by a foreign key will also
    be deleted. Are you sure you want to delete these content types?
    If you're unsure, answer 'no'.
    
        Type 'yes' to continue, or 'no' to cancel: yes
    

    It can be easy fixed by pressing pressing yes, that is really secure because table auth_message is unused by Django 1.4 and an old
    ContenType(name='message', app_label='auth', model='message')
    is related to it.

    If syncdb is run with enabled South, normal migration is done and nothing is reported, although it stay unfixed. It is delayed until syncdb is run later with disabled South.

    Currently it is more seamless to create a new database than to use an old. However historical versions of the file simple.db seems be very useful for dry testing of database upgrades.

  2. Log in to comment