Feature Request: Replacing default template system by a more powerful one: Jinja2

I have been working a lot with Django and I have always asked myself how is it possible that they decided to use Django Template system rather than Jinja2 , when it is way more intuitive, just like writing natural Python! Someone may argue that it's matte

Error

*Help with error:* AttributeError: 'NoneType' object has no attribute 'startswith' *Code added to settings.py:* MIGRATION_MODULES = {} for app in INSTALLED_APPS: if app: #print (app) MIGRATION_MODULES[app] = None print (MIGRATION_MODULES[app]) -- You received this

Re: Error

Please use django-users to get help with usage problems. On Friday, January 26, 2018 at 8:57:17 AM UTC-5, Anoosha Masood Keen wrote: > > > *Help with error:* > > > AttributeError: 'NoneType' object has no attribute 'startswith' > > > *Code added to settings.py:* > MIGRATION_MODULES = {} > for app

Re: Error

This error came while working with ticket #29039 On Friday, January 26, 2018 at 1:57:17 PM UTC, Anoosha Masood Keen wrote: > > > *Help with error:* > > > AttributeError: 'NoneType' object has no attribute 'startswith' > > > *Code added to settings.py:*

Re: Feature Request: Replacing default template system by a more powerful one: Jinja2

Switching the default template system would have a disruptive change on the Django ecosystem. For example, contrib.admin doesn't provide Jinja2 templates. I imagine there are third-party apps in the same situation. Here's a past thread about the same proposal: https://groups.google.com/d/topic/

Re: Error

As I mentioned in your other thread, you need to spend more time using Django before you work on a ticket that you don't understand. Also, this isn't the correct mailing list to get help with a ticket. I guess django-core-mentorship might be fine for that, or ask on the ticket itself. Please do

Fellow Report -- January 26, 2018

Hi All. This week I reviewed patches on: https://code.djangoproject.com/ticket/25790 -- Added option to disable column sort in admin changelist https://code.djangoproject.com/ticket/20118 -- Default authorization backend returns False when queried for object level permissions https://code.djan

select_related() for fetching individual fields

Hello, Provided: class M(models.Model): n = models.IntegerField() r = models.IntegerField() t = models.IntegerField() s = models.IntegerField() u = models.IntegerField() class F(models.Model): g = models.ForeignKey(M, on_delete=models.CASC

Re: select_related() for fetching individual fields

F.objects.select_related('g__n') looks a bit convoluted to me. You can already do something like F.objects.select_related('g').only('g__n', *[f.name for f in F._meta.get_fields()]) and write a small helper function for the list comprehension to avoid typing. Also I'd say it's generally a rare cas

Ticket #29066

Hello everyone ! I have two queries with respect to the ticket #29066 . 1. Do we need to provide an __neg__ operator for the Sum class, or its superclass Aggregate class ? Going by the description in the ticket, the operator should probably support