Nice one Matthias !
We might have something similar, in dal, discussion is undergoing:
https://github.com/yourlabs/django-autocomplete-light/issues/756#issuecomment-252368089
Currently ddf also renders json in a script tag in the middle of the form,
i think I might take the same direction as you
Thanks for the pointer! I think Django is misbehaving by importing "from
django.db.models import *" in "django/contrib/gis/db/models/__init__.py"
while django.db.models doesn't declare an __all__, so the "functions"
submodule can be imported there which obscures the version at
While we haven't decided of any particular format, you can expect the
announcements to look a bit
like
https://mta.openssl.org/pipermail/openssl-announce/2016-September/76.html
/Markus
On Friday, October 7, 2016 at 4:58:00 PM UTC+2, Tim Graham wrote:
>
> The Django team proposes [0] to
+1 from me. I really like this approach to help making my queries more DRY.
I also like how lightweight the library is altogether. Well done!
For those looking for a direct link, here you
go: https://github.com/Nepherhotep/django-orm-sugar
On Thursday, October 6, 2016 at 1:04:56 PM UTC-4,
The Django team proposes [0] to add the following to the security policy:
Approximately one week before public disclosure, ...
we notify django-announce [1] of the date and approximate time of the
upcoming security release. No information about the issues is given. This
is to
aid organizations
> So I suppose my question is this - are there any operations that return a
queryset that couldn't be captured in a Q object?
Annotations are a good example of operations that cannot be expressed in a
Q object.
On the ticket I suggested relying on the "sticky filter" feature of the ORM
to
Hi Tim,
Disappointingly, I don't think Django's doing anything off the wall here!
When you import a package's submodule, the name of that submodule is added
to the package's namespace. This is what allows you to put `import p.m`,
and to then to use `p.m` in your code -- module m is added to
Actually - my recollection was faulty. As the queryset method always has to
return a queryset (dur) I am not sure that I'm actually doing anything that
couldn't be expressed as a Q object. I'm just doing some funky stuff to get my
queryset in shape.
So I suppose my question is this - are there
In a few cases I've had to do filtering in Python because it wasn't possible
purely at the db level. (mainly in cases where I'm expected small result sets
obviously). I'd like to see this remain possible with any future changes.
--
You received this message because you are subscribed to the
