Django bugfix release: 3.2.6

[Carlton Gibson]

Details are available on the Django project weblog:

https://www.djangoproject.com/weblog/2021/aug/01/bugfix-release/ 


-- 
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/04867089-61B2-4963-AD4B-4D0E30207413%40gmail.com.

Re: datetime_safe deprecation

[Tim Graham]

Hi, did you consult the ticket? https://code.djangoproject.com/ticket/32738

On Sunday, August 1, 2021 at 1:09:04 PM UTC-4 mrhe...@gmail.com wrote:

> I note that datetime_safe is to be removed in Django 5.0 
> .
>   
> This module fixed the issue with the date padding for years < 1000, however 
> this issue still remains .
>
> Please can anyone advise what the guidance is to fix this date formatting 
> issue prior to the removal of the datetime_safe module?
>
> thank you
>

-- 
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/9cb806e7-614c-40fd-92f1-6eeef67afc32n%40googlegroups.com.

datetime_safe deprecation

[Matthew Hegarty]

I note that datetime_safe is to be removed in Django 5.0 
.
  
This module fixed the issue with the date padding for years < 1000, however 
this issue still remains .

Please can anyone advise what the guidance is to fix this date formatting 
issue prior to the removal of the datetime_safe module?

thank you

-- 
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/1636d626-637e-4712-869b-55447b9297b0n%40googlegroups.com.

Re: Fellow Reports -- July 2021

[Carlton Gibson]

Hi all. 


Calendar Week 29 -- ending 25 July.


Triaged:

https://code.djangoproject.com/ticket/32954 -- Improve error message with 
URLValidator and schemes (wontfix)
https://code.djangoproject.com/ticket/32949 -- decimal.InvalidOperation 
error on DecimalField form field (Accepted)



Reviewed:

https://github.com/django/django/pull/14650 -- Fixed #32930 - Added proper 
port number check in URLValidator
https://github.com/django/django/pull/14670 -- Fixed #31676 -- Updated 
organization docs according to DEP 0010.
https://github.com/django/django/pull/14645 -- Fixed #32949 -- Restored NaN 
and Inf handling in DecimalField.validate().



Authored:

https://github.com/django/django/pull/14678 -- Refs #32949 -- Adjusted 
release note wording.
https://github.com/django/django/pull/14669 -- Fixed #32365 -- Made 
zoneinfo the default timezone implementation.





Calendar Week 30 -- ending 01 August.


Triaged:

https://code.djangoproject.com/ticket/32953 -- Enable optional 
auto-reloading for testserver (wontfix)
https://code.djangoproject.com/ticket/32976 -- 502 Bad Gateway nginx/1.4.6 
(Ubuntu) (invalid)



Reviewed:

https://code.djangoproject.com/ticket/10244 -- FileFields can't be set to 
NULL in the db
https://github.com/django/django/pull/14716 -- Refs #32880 -- Made 
remaining titles consistent in how-to documents.
https://code.djangoproject.com/ticket/4 -- Non-nullable blank 
string-based model field validation doesn't prevent or clean `None`
https://code.djangoproject.com/ticket/27697 -- JSONField with blank=True is 
rendered as non-required field in a ModelForm
https://code.djangoproject.com/ticket/20205 -- PositiveIntegerfield does 
not handle empty values well
https://github.com/django/django/pull/14666 -- Fixed #20205 -- Failed model 
validation for empty strings in fields where empty_strings_allowed = False 
and blank = True.
https://github.com/django/django/pull/14651 -- Fixed #32933 -- Documented 
BoundField.initial as preferred over Form.get_initial_for_field().




Kind Regards,

Carlton


-- 
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/e1a12f00-219b-4976-8980-c53b44110096n%40googlegroups.com.

Re: FIleField(null=True) (Was: Guardrails around lack of model validation on blank=True fields)

[Carlton Gibson]

Hi Raffaele. Looking at #10244, it looks as if it needs someone to pick up 
Aymeric's suggestion. Would that be you? 😀
(Since you favour the option 2 there, I'd try that — it's probably OK with 
a suitable release note, as Aymeric said.) 
C. 

On Tuesday, 27 July 2021 at 23:46:33 UTC+2 Raffaele Salmaso wrote:

> Hi all,
> related to these tickets I want to remind this old ticket 
> https://code.djangoproject.com/ticket/10244 which needs a decision.
>
> Thanks!
>
> On Sun, Jul 25, 2021 at 3:12 PM Jacob Walls  wrote:
>
>> Hi group,
>>
>> We have several accepted tickets regarding developer headaches when a 
>> blank=True field, which skips model validation by design[1], contains 
>> inappropriate empty values (e.g. None for a not-nullable field or the empty 
>> string where empty strings aren't allowed). I want to see what the 
>> community thinks is reasonable here and move them to a resolution or 
>> potentially wontfix them.
>>
>> # 4 — CharField  (None 
>> from an application/json encoded payload isn’t cleaned to empty string)
>>
>> # 27697 — JSONField  (None 
>> isn’t cleaned to “{}”)
>>
>> # 20205 — PositiveIntegerField 
>>  (empty string unexpectedly 
>> passes model validation if blank=True. In this case the user was opting-in 
>> to model validation.)
>>
>> ***
>>
>> For 4—CharField—we could take Simon’s proposal 
>>  to last-minute 
>> cast None to empty string in get_db_prep_value() if the field’s 
>> empty_strings_allowed is True and null=False.
>>
>> For 27696—JSONField—similarly, we could cast from None to "{}" if 
>> null=False.
>>
>> For 20205—PositiveIntegerField, and by extension, any field where 
>> empty_strings_allowed is False—we might run model validation if we have an 
>> empty string to ensure we fail at the model level instead of the db, 
>> although this is not the usual practice for blank=True fields. See PR 
>> .
>>
>> The backwards compatibility concerns seem limited, because users are 
>> presumably working around these edge cases today, since invalid data is not 
>> being saved to the database. But there is the question of how much effort 
>> to expend here. I’m willing to see these through if we have a consensus 
>> around the best way to proceed.
>>
>> All best,
>>
>> Jacob
>>
>>
>> [1] blank=True and null=False and injecting-data-before-save being an 
>> idiom we don’t want to remove, see: 
>> https://code.djangoproject.com/ticket/4#comment:7
>>
>> -- 
>> 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-develop...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-developers/58616ad3-54b6-4b21-b252-96040680fa04n%40googlegroups.com
>>  
>> 
>> .
>>
>
>
> -- 
> | Raffaele Salmaso
> | https://salmaso.org
> | https://bitbucket.org/rsalmaso
> | https://github.com/rsalmaso
>

-- 
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/e694a082-48da-44bc-b3c0-5503176b91c9n%40googlegroups.com.