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

2017-01-07 Thread roboslone
> I do not think this matters, first off there is no commitment from our side > on type hinting or anything. We do not have any DEP or something related and > didn't even discuss if we actually want type hinting. Personally I am kinda > against it anyways, since it clutters the code for not

Re: Adding a middleware to match cookies

2017-01-07 Thread Tobias McNulty
On Jan 7, 2017 11:41 PM, "Jeff Willette" wrote: the specific case I am talking about deals with google analytics cookies, which are different for every user and sent with the request. When accessing request.user, I really only care about sessionid and csrftoken, if

Re: Adding a middleware to match cookies

2017-01-07 Thread Jeff Willette
the specific case I am talking about deals with google analytics cookies, which are different for every user and sent with the request. When accessing request.user, I really only care about sessionid and csrftoken, if present. So sending a vary by cookie header back will cause all the

Fellow Report - January 7, 2017

2017-01-07 Thread Tim Graham
Triaged --- https://code.djangoproject.com/ticket/27675 - Django postgres JSONField encoding (needsinfo) https://code.djangoproject.com/ticket/27679 - Document that empty formsets display min_num+extra forms (accepted) https://code.djangoproject.com/ticket/27690 - remove sleep before

Re: Adding a middleware to match cookies

2017-01-07 Thread Carl Meyer
On 01/07/2017 03:25 AM, Florian Apolloner wrote: > On Saturday, January 7, 2017 at 3:50:56 AM UTC+1, Jeff Willette wrote: > > What if there was an optional middleware early in the request > processing that matched cookies based on a regex in settings and > then modified the header to

Re: Adding a middleware to match cookies

2017-01-07 Thread Carl Meyer
On 01/06/2017 11:26 PM, Jeff Willette wrote: > Wy would this not help the efficiency of the downstream caches? Is it > because the request has already passed through them with the cookies > intact? and when it comes back through the response they have no way to > know they have been stripped?

Re: django-formtools is neglected/unmaintained

2017-01-07 Thread Tim Graham
django-formtools 2.0 is now available on PyPI. On Thursday, January 5, 2017 at 5:29:43 AM UTC-5, Romain Garrigues wrote: > > Hi guys, > > I'm currently investing some efforts to clean and make some django > packages up-to-date. > After django-dirtyfields

Presenting DCP, a compatibility layer for Django (feedback welcome)

2017-01-07 Thread Pkl
Hello, I've *at last* had some time to experiment with the idea I had thrown years again, of a system to workaround the recurring breakages introduced by new django releases, breakages which sometimes lead to unreconcilable requirements between django apps. After a sprint at PyconFR, with a

Re: Template handling of undefined variables

2017-01-07 Thread Tim Martin
On Friday, 6 January 2017 10:15:22 UTC, Alasdair Nicol wrote: > > Hi, > > On Thursday, 5 January 2017 17:51:39 UTC, Tim Martin wrote: >> >> >> >> On Thursday, 5 January 2017 04:15:31 UTC, Carl Meyer wrote: >>> >>> Hi Tim, >>> >>> On 01/04/2017 03:39 PM, Tim Martin wrote: >>> >>> > 1) There are

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

2017-01-07 Thread Tim Graham
Daniele, here's my try at being more concrete than "It seems reasonable" and "decent ledge of overlap". Let me know if you meant something different! "Django 2.0 will be the last version of Django to support Python 3.4. This allows those running older operating systems with Python 3.4 (such as

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

2017-01-07 Thread Florian Apolloner
On Saturday, January 7, 2017 at 4:03:43 AM UTC+1, Tim Graham wrote: > > I don't know if matters to anyone, but I guess as long as we support > Python 3.4 we can't do the type hinting project (PEP 484) since that's new > in 3.5? > I do not think this matters, first off there is no commitment

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

2017-01-07 Thread Daniele Procida
On Sat, Jan 7, 2017, Florian Apolloner wrote: >Not sure on how we'd put that into text, but something along the lines of >"we will support 3.4+ as long as feasible for us to do so" -- though I do >understand that this is like the same as saying: "We'll just support what

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

2017-01-07 Thread Florian Apolloner
Not sure on how we'd put that into text, but something along the lines of "we will support 3.4+ as long as feasible for us to do so" -- though I do understand that this is like the same as saying: "We'll just support what we want, how long we want" :D On Friday, January 6, 2017 at 2:33:24 PM

Re: Adding a middleware to match cookies

2017-01-07 Thread Florian Apolloner
Hi Jeff, On Saturday, January 7, 2017 at 3:50:56 AM UTC+1, Jeff Willette wrote: > > What if there was an optional middleware early in the request processing > that matched cookies based on a regex in settings and then modified the > header to only include the matched cookies? > I do not see

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

2017-01-07 Thread Daniel Moisset
Type hinting can be done in python 3.x by depending on the typing module (or inlining it). Type hinting for instance/class attributes will have a much nicer syntax in python 3.6 only (PEP 526) Best, D. On 7 January 2017 at 03:03, Tim Graham wrote: > I don't know if