ticket 28404

[Georgiy Nazarov]

Hello!

Was there any consensus does ticket 28404 
 need to be fixed? And how 
should it be fixed, just by showing empty_value_display in case of empty 
(not None) string or by separating cases of empty and None values?

--
Georgiy Nazarov

-- 
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/4f6c0069-e872-4727-900d-72647d417bc9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ticket 28404

[Tim Graham]

No, there hasn't been any discussion about it. Do you have a use case for 
solving the ticket that might inform the decision?

On Saturday, November 4, 2017 at 1:01:22 PM UTC-4, Georgiy Nazarov wrote:
>
> Hello!
>
> Was there any consensus does ticket 28404 
>  need to be fixed? And how 
> should it be fixed, just by showing empty_value_display in case of empty 
> (not None) string or by separating cases of empty and None values?
>
> --
> Georgiy Nazarov
>

-- 
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/8b23cb43-c10f-40c2-b5ca-82ebb60bc88b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Fellow Report - November 4, 2017

[Tim Graham]

Triaged

---

https://code.djangoproject.com/ticket/28753 - Unit tests documentation does 
not specify non-python requirements (worksforme)

https://code.djangoproject.com/ticket/28756 - QuerySet API .extra( ) usage 
for FIELD + ORDER BY of queryset (invalid)

https://code.djangoproject.com/ticket/28757 - Allow using forms of 
contrib.auth without installing contrib.auth (accepted)

https://code.djangoproject.com/ticket/28746 - Model missing custom Meta 
option in migrations (invalid)

https://code.djangoproject.com/ticket/28745 - Add first page and last page 
links to paginator docs example (fixed)

https://code.djangoproject.com/ticket/28764 - Store staticfiles.json with 
code (duplicate)

Authored

--

https://github.com/django/django/pull/9327 - Fixed #28770 -- Warned that 
quoting a placeholder in a raw SQL string can lead to SQL injection.

Reviewed/committed

--

https://github.com/django/django/pull/9305 - Fixed #28742 -- Fixed 
AttributeError crash when assigning None to cached reverse relations.

https://github.com/django/django/pull/9311 - Fixed #28760 -- Removed 
DummyCache's unnecessary get/set/delete_many().

https://github.com/django/django/pull/9306 - Fixed #28750 -- Allowed models 
to define Meta.manager_inheritance_from_future for backwards compatibility.

https://github.com/django/django/pull/9300 - Fixed #28749 -- Added subquery 
support for ArrayField's __in lookup.

https://github.com/django/django/pull/9259 -Fixed #28723 -- Fixed 
RelatedManager's prefetch_related() cache name. 

https://github.com/django/django/pull/9050 - Fixed #28571 -- Added a prompt 
to bypass password validation in createsuperuser.
https://github.com/django/django/pull/9319 - Refs #17448, #28632 -- Fixes 
related to usage of raw SQL with GIS.

-- 
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/ed9cabb0-8117-4a52-a2e9-c50e7da50c81%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.