Fellow Report - January 6, 2018

2018-01-06 Thread Tim Graham


Triaged

---

https://code.djangoproject.com/ticket/28975 - Skip automatic creation of 
postgis extension if it already exists (accepted)

https://code.djangoproject.com/ticket/28980 - Make the autodetector 
validate the type of one-off default values (accepted)

https://code.djangoproject.com/ticket/28981 - GeoIP2 should error when 
GEOIP_PATH exists but there is no MaxMind database (accepted)

https://code.djangoproject.com/ticket/28970 - Option to suppress signals on 
save to avoid loop (wontfix)

https://code.djangoproject.com/ticket/28985 - Remove None checking before 
hasattr() (fixed)

https://code.djangoproject.com/ticket/28987 - Migration changing 
ManyToManyField target to 'self' doesn't work correctly (accepted)

https://code.djangoproject.com/ticket/28982 - Simplify code with "and" and 
"or" (fixed)

Reviewed/committed

--

https://github.com/django/django/pull/9513 - Fixed #28974 -- Made 
refresh_from_db() hint routers about its instance.

https://github.com/django/django/pull/9526 - Fixed #28902 -- Fixed 
password_validators_help_text_html() double escaping.

https://github.com/django/django/pull/9517 - Fixed #28867 -- Added system 
check for a model property that clashes with a related field accessor.

https://github.com/django/django/pull/9407 - Refs #15902 -- Made 
set_language() view always set the current language in a cookie.

https://github.com/django/django/pull/9530 - Fixed #28986 -- Prevented 
boolean values in admin list display from being formatted with thousand 
separators.

https://github.com/django/django/pull/8958 - Fixed #28517 -- Fixed admin 
delete confirmation view crash when related models don't have a delete 
permission.

https://github.com/django/django/pull/9535 - Fixed #28859 -- Made Oracle 
backend raise DatabaseError if "no data found" exception is hidden by 
Oracle OCI library.

https://github.com/django/django/pull/9354 - Fixed #28757 -- Allowed using 
contrib.auth forms without installing contrib.auth.

https://github.com/django/django/pull/9415 - Fixed #28882 -- Fixed cleaning 
of disabled MultiValueFields.
https://github.com/django/django/pull/8990 - Fixed #15522 -- Added 
ModelAdmin.delete_queryset() to customize "delete selected objects" 
deletion.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/1a97c957-3cf5-4b3c-8498-9eddb918b6fc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: QueryDict and ordering

2018-01-06 Thread Todor Velichkov
Is this what you are looking for?


from django.http import QueryDict
from collections import OrderedDict

class OrderedQueryDict(QueryDict, OrderedDict):
pass

my_dict = OrderedQueryDict(request.META['QUERY_STRING'])

print my_dict.items()



On Friday, January 5, 2018 at 5:07:41 PM UTC+2, Ole Laursen wrote:
>
> Hi!
>
> Would it be possible to derive QueryDict (i.e. MultiValueDict) from an 
> OrderedDict instead of dict?
>
> I'm finding it increasingly irritating that the original order is kept by 
> the whole stack right until Django puts it into a dict. It makes some 
> highly dynamic form situations more tedious to handle.
>
> Now that Python 3.6 preserves the order of dicts as an implementation 
> detail, there should not be any performance overhead as far as I'm aware.
>
>
> Ole
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/1913a9a7-e2e2-4373-8486-7ffd9bbf53fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.