Hello everyone!
I'm conducting a PR cleanse crusade for the project, where I'll try move
forward those PRs that still make sense or close them when appropriate.
Were there other developments in this topic that would be relevant to make
a decision about the PR[0]?
Thank you!
Natalia.
[0] https
Hello everyone!
I was wondering if we could make a decision about this topic. On the one
hand, and as far as I understand, the forum is the preferred channel of
communication. On the other hand, having multiple channels of communication
can spread important discussions too thin, making it diffi
;
>> On Thu, 4 May 2023, at 15:19, Arthur Rio wrote:
>>
>> Yes please!
>>
>>
>>
>> On May 3, 2023 at 11:19:12 PM, jure.er...@gmail.com (jure.er...@gmail.com)
>> wrote:
>>
>>
>> +1
>>
>>
>>
>> *From:* django-d...@goo
Week ending 2023-05-07 (week 19)
Triaged:
https://code.djangoproject.com/ticket/34531 - Rendering form throws
deprecation warning (invalid)
https://code.djangoproject.com/ticket/34539 - `get_prep_value` no longer
called for JSONField (accepted with ongoing conversations)
https://code.djang
Hello everyone!
I've posted my fellow report in the
forum: https://forum.djangoproject.com/t/django-fellow-report-natalia/20942
Following reports will be threaded in that topic \o/
Thank you! Natalia.
On Monday, May 8, 2023 at 9:33:15 AM UTC-3 natali...@gmail.com wrote:
> Week ending
On Thursday, November 10, 2022 at 5:40:45 AM UTC-3 Jacob Rief wrote:
How about ditching the JS based datepicker altogether and replace it
against the built-in datepicker offered by modern browsers? This would also
help users of mobile devices because they already have good internal
implementa
