Re: Plugins can be hidden when changing Page Template

2017-08-09 Thread czpython
Hello @Martin, Because plugins have a direct relationship to their placeholders, I would rather not move these automatically every time the user changes a page's template. This can cause sync problems, as well as other data corruptions. That said, when a template changes, the placeholders

Re: Admin list view counting

2017-08-09 Thread Adam Johnson
FYI Django-MySQL supplies an approx_count() method: https://django-mysql.readthedocs.io/en/latest/queryset_extensions.html#django_mysql.models.approx_count . It only works on QuerySets without filters. From what I understand it's possible to get an estimate for filtered queries in MySQL in *some*

Re: Django 2.0 Python version support (Python 3.6+ only?)

2017-08-09 Thread Joe Tennies
Looking at the list, I think the only gain that required 3.5+ was typing. The performance was due to which version was installed and not a real feature. That stated, should the installer add typing from pypi as a requirement (assuming someone adds typing info). On Wed, Aug 9, 2017, 3:01 AM

Oracle sequence naming regression - input on approach?

2017-08-09 Thread Kevin Grinberg
Hi folks, I'm looking for input on https://code.djangoproject.com/ticket/28451 Basically, the root of the issue is that a change introduced in 1.11 breaks Oracle sequence names under certain conditions (if you have use_returning_into = False, which is *not* the default). The symptom is that

Re: Django 2.0 Python version support (Python 3.6+ only?)

2017-08-09 Thread Aymeric Augustin
Hello, I took a look at this thread again and I still reach the same conclusion as Claude. Best regards, -- Aymeric. > On 9 Aug 2017, at 09:02, Claude Paroz wrote: > > Le mardi 8 août 2017 01:45:55 UTC+2, Tim Graham a écrit : > Has anyone changed their thinking in the

Re: Django 2.0 Python version support (Python 3.6+ only?)

2017-08-09 Thread Claude Paroz
Le mardi 8 août 2017 01:45:55 UTC+2, Tim Graham a écrit : > Has anyone changed their thinking in the last few months? If not, I guess > we'll keep Python 3.4 support for Django 2.0 and drop it for 2.1. > I am not strongly opposed to dropping 3.4 support, but I still think we should keep it for