Migration to Django 1.4.1 : nothing about auth.message in Backward incompatibilities CHANGELOG.

244 views
Skip to first unread message

Stan

unread,
Sep 21, 2012, 10:06:31 AM9/21/12
to django-d...@googlegroups.com
Hi,

Maybe I missed something but in upgrading a project from Django 1.3.x to 1.4.1 I have encounter the following error when running my tests :

Problem installing fixture '/Users/stan/Dropbox/Projets/Aden/Publish-dj1.4/fab4/../fab4/parametrage/fixtures/tests/auth.json': Traceback (most recent call last):
  File "/Users/stan/src/venv-dj-1.4/lib/python2.6/site-packages/django/core/management/commands/loaddata.py", line 190, in handle
    for obj in objects:
  File "/Users/stan/src/venv-dj-1.4/lib/python2.6/site-packages/django/core/serializers/json.py", line 49, in Deserializer
    raise DeserializationError(e)
DeserializationError: ContentType matching query does not exist.



It appears that the contenttype table created in the test database (syncdb too I presume) does not contains anymore the following row :

+----+----------------------------------------+--------------+-------------------------------+
| id | name                                   | app_label    | model                         |
+----+----------------------------------------+--------------+-------------------------------+
|  4 | message                                | auth         | message                       |



(Running the tests in django 1.3 is just fine)

Because debugging fixtures is a real pain (It always end with pdb :-), maybe a note in Changelog or something could save time to a bunch of people ?

Cheers !

Stanislas.


Aymeric Augustin

unread,
Sep 21, 2012, 10:17:59 AM9/21/12
to django-d...@googlegroups.com
Hi Stanislas,

Since the user message framework was deprecated in Django 1.2, its deprecation is documented in the 1.2 release notes:

The features deprecated in Django 1.2 and eventually removed in Django 1.4 are listed in the deprecation timeline:

In the future, we're going to link more prominently to this deprecation timeline. Although it's mentioned in the very first paragraph of the release notes, it's often overlooked. Here's a preview of the 1.5 release notes:

Cheers,

-- 
Aymeric.


--
You received this message because you are subscribed to the Google Groups "Django developers" group.
To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/-iKnHzJASb8J.
To post to this group, send email to django-d...@googlegroups.com.
To unsubscribe from this group, send email to django-develop...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.

-- 
Aymeric.



Stan

unread,
Sep 21, 2012, 3:00:40 PM9/21/12
to django-d...@googlegroups.com


On Friday, September 21, 2012 4:18:35 PM UTC+2, Aymeric Augustin wrote:
Hi Stanislas,

Since the user message framework was deprecated in Django 1.2, its deprecation is documented in the 1.2 release notes:

I had missed that one :-)
 
Thanks.

Reply all
Reply to author
Forward
0 new messages