Hi Luke,
I have been thinking and researching a lot recently about SQLalchemy and
django integration.
Now SQLalchemy provides a devlarative orm extension too quite identical to
django orm[not same], django has also refactored a lot in db internals with
model meta refactore, expressions, new mi
>
> Also, some random feature requests:
>
>- .values(‘stuff’, my_thing=Coalesce(‘thing’, ‘stuff’)) should work
>
> I thought this was already tracked but I couldn't find an existing
ticket. So I created it: https://code.djangoproject.com/ticket/25871
Feel free to leave comments there if
No we haven't done that before. I think advertising it in the blog post and
release notes would be enough. In particular, I'd like to advertise it as a
tentative plan just in case someone comes along after we advertise the plan
more widely and offers a compelling reason to continue Python 3.2 su
Now that the django admin supports the Content-Security-Policy header I
think merging django-csp into contrib would be a good fix for
https://code.djangoproject.com/ticket/15727
It might also be an idea to wait for Mozilla to also respond to the
proposal of this merger.
See my PR here: https:
Triaged
---
https://code.djangoproject.com/ticket/25808 - Setting to allow
django.test.Client default requests to follow=True (wontfix)
https://code.djangoproject.com/ticket/25840 - cache.get_or_set() works
incorrectly with DummyCache backend (accepted)
https://code.djangoproject.com/ti
Hello,
> On 5 déc. 2015, at 10:28, Raphael Gaschignard wrote:
>
> A behaviour that exemplifies this is that
> queryset.annotate(foo=thing).annotate(bar=other_thing) is not the same as
> queryset.annotate(foo=thing, bar=other_thing) given certain things. This goes
> against the intuitive int
Hi list,
I want to preface this by saying I’m really glad to see the ORM where it
is in 1.8, it’s gotten really far and I now think it’s not hopeless to
imagine writing complex things in the ORM…
So earlier this week I wrote a bit of a rant in the bug tracker about
how annotate is con
Basically, the origin check would only be useful for safari (in this case).
Everywhere else we'd still need to rely on the referrer header.
On Sat, Dec 5, 2015 at 3:42 AM, Florian Apolloner
wrote:
>
>
> On Friday, December 4, 2015 at 8:03:45 PM UTC+1, Flávio Junior wrote:
>>
>> I can create a ti
On Friday, December 4, 2015 at 8:03:45 PM UTC+1, Flávio Junior wrote:
>
> I can create a ticket suggesting Django to check Origin header before
> checking Referer. Or do you want to create that Collin?
>
I think Firxfox does not send the origin header ever yet, do you have any
docs on that (As