Re: Fellow Reports - August 2019

[Mariusz Felisiak]

Week ending August 11, 2019.

*Triaged:*
https://code.djangoproject.com/ticket/30674 - Autoreload fails to restart 
server when exception is SyntaxError. (duplicate)
https://code.djangoproject.com/ticket/30678 - Confirm support for GDAL 3.0. 
(accepted)
https://code.djangoproject.com/ticket/30680 - Remove security.W007 check. 
(accepted)
https://code.djangoproject.com/ticket/30679 - Warn when Django works with 
unsupported version of GDAL. (wontfix)
https://code.djangoproject.com/ticket/30682 - Bug with Mysql connection 
(since 2.2a1). (duplicate)
https://code.djangoproject.com/ticket/30681 - SQL script from 
sqlsequencereset doesn't work on Postgres 11.3. (worksforme)
https://code.djangoproject.com/ticket/30683 - QuerySet.count() crashes when 
window functions and conditional expressions are both used. (duplicate)
https://code.djangoproject.com/ticket/30696 - Remove obsolete mention of 
CheckConstraint in AddConstraint docs. (accepted)
https://code.djangoproject.com/ticket/30697 - SQLite3.28 breaks django 
migrations. (wontfix)
https://code.djangoproject.com/ticket/30695 - Fix an example of Storage 
objects in Managing files docs. (accepted)

*Reviewed/committed:*
https://github.com/django/django/pull/11622 - Fixed #28393 -- Added helpful 
error messages for invalid AutoField/FloatField/IntegerField values.
https://github.com/django/django/pull/11631 - Fixed #30680 -- Removed 
obsolete system check for SECURE_BROWSER_XSS_FILTER setting.
https://github.com/django/django/pull/11630 - Fixed #30673 -- Relaxed 
system check for db_table collision when database routers are installed by 
turning the error into a warning.
https://github.com/django/django/pull/11620 - Fixed #29008 -- Fixed crash 
of 404 debug page when URL path converter raises Http404.
https://github.com/django/django/pull/11646 - Fixed #30670 -- Doc'd 
SchemaEditor.add/remove_constraint().
https://github.com/django/django/pull/11649 - Fixed #30696 -- Removed 
obsolete mention of CheckConstraint in the AddConstraint docs.
https://github.com/django/django/pull/11638 - Fixed #30677 -- Improved 
error message for urlencode() and Client when None is passed as data.

I was off for almost entire week and I will be less active for the next two 
weeks because I have a newborn on board .

Best regards,
Mariusz

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/e8292fd7-8586-476d-bcd6-60bcc1edbdbf%40googlegroups.com.

Re: Display labels for autocomplete fields

[bjw]

Actually, I can think of occasions where what is displayed would vary depending 
on which model the FK was from,  not only on the model that is the target.

bjw 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/c05cce80-dd59-497e-a6b1-606cfbfa58bf%40googlegroups.com.

Re: Display labels for autocomplete fields

[Janez Kranjc]

You don't need one for each field. You need one per model - similar to 
__str__

On Sunday, August 11, 2019 at 3:54:03 PM UTC+2, 1337 Shadow Hacker wrote:
>
>
> Would it be possible to add a `search_display_fields` on the relevant 
>> ModelAdmin, alongside `search_fields` to customise the display in the form 
>> select box? This could be either a model field or a callable on the model 
>> or modeladmin.
>>
>
> Another suggestion is to add get_FIELD_autocomplete_display(), to the 
> model or teh ModelAdmin
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/30a9993b-2a4c-4996-9fab-3b31eceeb944%40googlegroups.com.

Re: Display labels for autocomplete fields

['1337 Shadow Hacker' via Django developers (Contributions to Django itself)]

>> Would it be possible to add a `search_display_fields` on the relevant 
>> ModelAdmin, alongside `search_fields` to customise the display in the form 
>> select box? This could be either a model field or a callable on the model or 
>> modeladmin.

Another suggestion is to add get_FIELD_autocomplete_display(), to the model or 
teh ModelAdmin

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/lRaN6wQSqzdeDboF0UO79hAP6jbDoqEXN-xbz32hgU8HRkO4Pvj_bySMpQ7OTO2rB0aNcACTpMF040vUnGEkH74oBgaQDMIyjTG_wDzqeHw%3D%40protonmail.com.

Re: Django Websocket Implementation Request

['1337 Shadow Hacker' via Django developers (Contributions to Django itself)]

> They're not that popular actually, it seems...

They might become more popular, when they work behind proxies ... a limitation 
which you usually figure out after your first important client tries to connect 
from behind their corporate proxy, then you can implement polling again - a 
fallback that socket.io provides.

However, websockets are nice to have if you're using a Django library that 
supports data binding such as ryzom, maybe there are others but I'm not aware 
about them, and it doesn't implement the polling fallback so far afaik.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/STfktCMulCv9lYeEfdC96aFUmH4Y2_wz90LV9_15nmhqr0YCuThgrCJcZ32N3odKDtR0TThEBgxdxV_j-yjuZZNVHGwRE7bQ77mmiv0TVw8%3D%40protonmail.com.

Re: Django LTS support time

['1337 Shadow Hacker' via Django developers (Contributions to Django itself)]

Hi,

Lean Sensei practicing Django since 2008 here. Have tried all sorts of 
strategies, the one that offers the best effort/ROI ratio is to upgrade as soon 
as a new version comes out, even if that means contributing patches to 
dependencies and deploying forks until patches are released.

Best of luck

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/GrEY9QLXy903LnYwLvv54Irn2hUfGJlearm6hNR6KgRJV0awYTwQxgyLpUbN-BRrZJJQD5HzC7okEKiX-OVH8tlTQXjPqaFJVuka62cTaqk%3D%40protonmail.com.

Request for closing #25139 -- ModelFormSet: allow swapping unique values

[PARTH PATIL]

Hey can someone please have look at this ticket, I feel the requested 
feature is not really feasible to implement, also it's not applicable in 
the general case.

I don't think so this is feasible, this will require n(n-1)/2 comparisons 
to determine whether any two of the models are swapped.
This looks easy in the above case but won't be a good idea for a general 
case.

Correct me if I'm wrong or if anyone has a better approach for 
implementation of this feature. I would like to work on it.

But as of now, I feel this ticket should be closed


Here is a link to the ticket 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/61c73eca-c618-4c11-b5e6-6feaf407e8e6%40googlegroups.com.