Re: Fellow Reports -- November 2019

2019-12-01 Thread Carlton Gibson
Hi all. 



Calendar Week 48 -- ending 01 December.


Preparation for Django 3.0 and other releases.


Triaged:

https://code.djangoproject.com/ticket/30974 -- Selenium asserts should be 
wait statements (Duplicate of #29892)
https://code.djangoproject.com/ticket/31035 -- Promote 
BaseCommand.run_from_argv to a documented method (wontfix)
https://code.djangoproject.com/ticket/31034 -- Add a navigation sidebar to 
the admin (Accepted)


Reviewed:

https://github.com/django/django/pull/12098 -- Refs #23919 -- Replaced 
super(...) with super() in metaclasses.
https://github.com/django/django/pull/12139 -- Fixed #31028 -- Used 
classList API to check, add and remove DOM classes.
https://github.com/django/django/pull/12154 -- Fixed #30953 -- Made 
select_for_update() lock only queryset's model when using 
"self" with multi-table inheritance.
https://github.com/django/django/pull/12151 -- Fixed #31042 -- Removed 
AdminSeleniumTestCase.get_css_value() in favor of Selenium .is_displayed().
https://github.com/django/django/pull/12147 -- Refs #29892 -- Replaced 
Selenium .submit() shim with .click() on the submit button.
https://github.com/django/django/pull/12052 -- Fixed #30974 -- Fixed some 
selenium race conditions using wait over assert
https://github.com/django/django/pull/12053 -- Fixed #30975 -- Replaced 
custom get_select_option with Selenium's select_by_value.
https://github.com/django/django/pull/12133 -- Fixed #31026 -- Switch from 
rendering to template engine
https://github.com/django/django/pull/12051 -- Fixed #30973 -- Converted 
selenium tests wait_page_loaded() to context manager.
https://github.com/django/django/pull/12149 -- Fixed #29892 -- Fixed 
Selenium tests to pass with Firefox.
https://github.com/django/django/pull/12141 -- Fixed #30803 -- Allowed 
comma separators for milliseconds in django.utils.dateparse functions.



Authored:

https://github.com/django/django/pull/12152 -- Fixed #29892 -- Added 
explicit Selenium wait in admin autocomplete tests.



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/419434bd-dd4f-4f90-9ca0-20a3c3b92b0e%40googlegroups.com.


Re: Status of 3.0 release blockers

2019-12-01 Thread Recai Atak
Hi Carlton ,

i saw it somewhere , django 3.0 is coming with async database transaction 
availability . is that right ?

10 Eylül 2019 Salı 11:56:51 UTC+3 tarihinde Carlton Gibson yazdı:
>
> Hi all. 
>
> Time to begin the release process for 3.0! 🎉
>
> The feature freeze was yesterday, with some last things making it over the 
> line. 
>
> Claude has updated the translations catalogs already. 
>
> Mariusz and Simon have cleaned up the last release blocker this morning, 
> so we've branched 
> stable/3.0.x and we're ready to go with 3.0 alpha 1 today. 
>
> The schedule[0] is for the alpha today, beta in a month or so, release 
> candidate a month after that. 
> Final release is due December 2nd. 
>
> https://code.djangoproject.com/wiki/Version3.0Roadmap#schedule
>
> We will use this thread to update on any changes. 
> To that, please test early and often. 
>
> Thanks all for your super efforts on this release cycle! 
>
> 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/beb90e11-ee20-4826-b22b-e1a8af69407a%40googlegroups.com.


Let Django users customize FORMAT_SETTINGS (a feature request)

2019-12-01 Thread אורי
Django developers,

I just added this feature request:
https://code.djangoproject.com/ticket/31052

I customized FORMAT_SETTINGS in Speedy Net, you can see more information in
this commit:
https://github.com/speedy-net/speedy-net/commit/f5dc4896c136a816ab9fe0dc360d3fd59d0a5f33


And on Stack Overflow:
https://stackoverflow.com/questions/57188435/django-how-do-i-override-default-date-formats-per-locale

To customize FORMAT_SETTINGS I had to patch 14 files, because the tests
failed and I had to patch the tests too. Is it possible to let Django users
customize FORMAT_SETTINGS without having to patch files? For example you
can check if the settings contain FORMAT_SETTINGS, and if it is - include
these settings in the global FORMAT_SETTINGS (a union, like in the above
commit).

formats.FORMAT_SETTINGS =
formats.FORMAT_SETTINGS.union(django_settings.FORMAT_SETTINGS)

אורי
u...@speedy.net

-- 
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/CABD5YeEY9Eq60MYmru_7hq%2BeLkzpJenn0CvXc8c12UEOEpF4%2BA%40mail.gmail.com.


Re: Let Django users customize FORMAT_SETTINGS (a feature request)

2019-12-01 Thread אורי
Hi,

If you accept this feature request I can try to write it myself as a pull
request to Django.

אורי
u...@speedy.net


‪On Mon, Dec 2, 2019 at 6:32 AM ‫אורי‬‎  wrote:‬

> Django developers,
>
> I just added this feature request:
> https://code.djangoproject.com/ticket/31052
>
> I customized FORMAT_SETTINGS in Speedy Net, you can see more information
> in this commit:
>
> https://github.com/speedy-net/speedy-net/commit/f5dc4896c136a816ab9fe0dc360d3fd59d0a5f33
>
>
> And on Stack Overflow:
>
> https://stackoverflow.com/questions/57188435/django-how-do-i-override-default-date-formats-per-locale
>
> To customize FORMAT_SETTINGS I had to patch 14 files, because the tests
> failed and I had to patch the tests too. Is it possible to let Django users
> customize FORMAT_SETTINGS without having to patch files? For example you
> can check if the settings contain FORMAT_SETTINGS, and if it is - include
> these settings in the global FORMAT_SETTINGS (a union, like in the above
> commit).
>
> formats.FORMAT_SETTINGS =
> formats.FORMAT_SETTINGS.union(django_settings.FORMAT_SETTINGS)
>
> אורי
> u...@speedy.net
>

-- 
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/CABD5YeFZqOWFQScXSoZnV%2B-NSNqots9co9o7KAuEHZiH74qQtA%40mail.gmail.com.


Re: Status of 3.0 release blockers

2019-12-01 Thread Adam Johnson
Recai, I’m afraid that’s not true. Django 3.0 adds ASGI support for
asynchronous calls to the outermost handler. However all the rest of the
stack remains synchronous. See the release notes:
https://docs.djangoproject.com/en/dev/releases/3.0/

For a single file demo app see my blog post:
https://adamj.eu/tech/2019/09/14/a-single-file-async-django-app/


On Sun, 1 Dec 2019 at 20:05, Recai Atak  wrote:

> Hi Carlton ,
>
> i saw it somewhere , django 3.0 is coming with async database transaction
> availability . is that right ?
>
> 10 Eylül 2019 Salı 11:56:51 UTC+3 tarihinde Carlton Gibson yazdı:
>>
>> Hi all.
>>
>> Time to begin the release process for 3.0! 🎉
>>
>> The feature freeze was yesterday, with some last things making it over
>> the line.
>>
>> Claude has updated the translations catalogs already.
>>
>> Mariusz and Simon have cleaned up the last release blocker this morning,
>> so we've branched
>> stable/3.0.x and we're ready to go with 3.0 alpha 1 today.
>>
>> The schedule[0] is for the alpha today, beta in a month or so, release
>> candidate a month after that.
>> Final release is due December 2nd.
>>
>> https://code.djangoproject.com/wiki/Version3.0Roadmap#schedule
>>
>> We will use this thread to update on any changes.
>> To that, please test early and often.
>>
>> Thanks all for your super efforts on this release cycle!
>>
>> 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/beb90e11-ee20-4826-b22b-e1a8af69407a%40googlegroups.com
> 
> .
>
-- 
Adam

-- 
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/CAMyDDM3LuPzEUC4wjEjXmdeCqxx%2BUtVDOM60LXogSQpRK9WL%2BQ%40mail.gmail.com.