Django 1.7, KeyError: u'manager' error

I had a problem in using django 1.7. Example: class ModelA(models.Model): fielda = models.CharField(max_length=10) class ModelsB(models.Model): modela = models.ForeignKey(ModelA) fieldb = models.CharField(max_length=10) when I query like " modela_instance.modelb_set()', I will get

Re: Django 1.7, KeyError: u'manager' error

By using the API correctly: https://docs.djangoproject.com/en/1.7/topics/db/queries/#backwards-related-objects Also, this mailing list is not the correct place to ask these questions, you're looking for https://docs.djangoproject.com/en/1.7/internals/mailing-lists/#django-users On Fri, Oct 17,

Re: Django 1.7, KeyError: u'manager' error

Hi Taenyon, This list is for development on Django itself. I see you've also asked the question on the `django-users` mailing list, which is the right mailing list for your question. You'll want to follow up any further questions on the `django-users` thread rather than this one. All the best,

Re: Multiple template engines for Django - week 1

On Sun, 2014-10-12 at 20:31 +0200, Aymeric Augustin wrote: > Feedback is welcome, especially on sections I've described as "done" in the > update. The FAQ section says that template context processors isn't going to be supported for context processors. The context processors return a dictionary

Re: Multiple template engines for Django - week 1

Hi Anssi, On 17 oct. 2014, at 14:49, Anssi Kääriäinen wrote: > The FAQ section says that template context processors isn't going to be > supported for context processors. Indeed, at this time, my theoretical position is not to enforce such an API and leave it up to

Re: Django detects HTTP Accept-Language header in case-sensitive manner

On 10/16/2014 09:41 PM, Wayne Ye wrote: > HI Carl and Ramiro, > Thank you both very much for tracking this issue! > > Actually I am a junior Django developer (but has nearly 10 years exp on > ASP.NET and RoR), I am eager to contribute to the Django project! If > this issue has not yet been

1.8 release planning

I'd like to kickoff the discussion on the timetable and process for the 1.8 release. I am also volunteering to be the release manager. First, a retrospective on the 1.7 release with planned release dates and (actual): Jan. 20: alpha (Jan. 22) March 6: beta (March 20) May 1: RC (June 26) May

Re: 1.8 release planning

I was wondering when this discussion was going to happen - it's good to see some dates finally proposed, thanks Tim. The LTS proposal is a good one. It should give people enough time (6 months) to jump to the next LTS release. I also think that 1.8 should be a good candidate for LTS.

Re: 1.8 release planning

If you are upgrading from 1.4, I would recommend going step by step through each intermediate Django version. I don't believe trying to upgrade straight away to 1.8 would be easier. I'd encourage anyone on 1.4 to start doing intermediate upgrades soon, so if there are still undetected

Re: A new approach for migrations?

Thanks Shai! That trick helped me a lot. I eventually managed to add migrations successfully using this trick and some manual adjustments to the migration files. I'm optimistic that things will flow more easily from now on. Migrations is such an awesome addition to django, but I have to admit