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: > https://docs.djangoproject.com/en/1.4/releases/1.2/#user-messages-api >
I had missed that one :-) Thanks. > The features deprecated in Django 1.2 and eventually removed in Django 1.4 > are listed in the deprecation timeline: > https://docs.djangoproject.com/en/1.4/internals/deprecation/#id2 > > 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: > > https://docs.djangoproject.com/en/dev/releases/1.5/#backwards-incompatible-changes-in-1-5 > > Cheers, > > -- > Aymeric. > > > Le 21 sept. 2012 à 16:06, Stan <[email protected] <javascript:>> a > écrit : > > 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. > > > > -- > 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 [email protected]<javascript:> > . > To unsubscribe from this group, send email to > [email protected] <javascript:>. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > > -- > 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/-/NKfnjoRkvqgJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
