On Wed, Jul 2, 2014 at 3:48 PM, Frank Bieniek <frank.bien...@produktlaunch.de> wrote: > Hi all, > does currently anybody upgrade his > django 1.6 projects with south and tastypie to the new django1.7 > > Resources definition of Tastypie collids with the new app registry loading. > > I do want to upgrade the project to django 1.7 > but I can not replace the whole rest api app - > "an upgrade fork idea" would be great. > > Thats the problem: > class MyResource(ModelResource): > ... > class Meta: > queryset = AnyModel.objects.all() > > Some models just hit the AppRegistryNotReady Exception... > > Any Ideas/Hints/Magic are welcome > > Thanks > Frank >
Four options (and these are basically the same for any third party library you use) 1) Wait for Tastypie developers to add support for Django 1.7 to a release, using 1.6 in the meantime 2) Add support for Django 1.7 to Tastypie and send the patch to Tastypie developers 3) Hire someone to do 2) 4) Work around the issue if possible Tastypie is a very popular framework, so I would expect them to have a release out that supports Django 1.7 soon after Django 1.7 is actually released. As a work around, can you give a callable as the "queryset" attribute on your resource meta class? Cheers Tom -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAFHbX1KMQuBR3e7Vdp0Xqc7CumyWE5w81G%2BQqF9OOf1UQDD4DQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
