Roadmap and communication of features planned for releases
This came up via a query at Reddit https://reddit.com/r/django/comments/setc9n/official_roadmap/ and I wasn’t able to find anything other than what is already in the comments. That also made me curious and feel that more communication about planned features and changes could be useful. Thanks! -- 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/27b5c12d-6473-4831-a635-47d01de55249n%40googlegroups.com.
Re: Roadmap and communication of features planned for releases
Hi Jason, I'm not aware of any formally planned features. (If there were any, I'd expect they'd be discussed on this mailing list.) The next release will include whatever features the community contributes by the feature freeze deadline. See https://code.djangoproject.com/wiki/Version4.1Roadmap for the timetable. On Saturday, January 29, 2022 at 8:41:01 AM UTC-5 Jason Johns wrote: > This came up via a query at Reddit > https://reddit.com/r/django/comments/setc9n/official_roadmap/ and I > wasn’t able to find anything other than what is already in the comments. > That also made me curious and feel that more communication about planned > features and changes could be useful. > > Thanks! > > > -- 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/00b41a73-4480-4948-8815-f77502f58801n%40googlegroups.com.
Re: Preparing Django code for the Black stable release
Hi all, Black 22.1.0 has just been released https://github.com/psf/black/releases/tag/22.1.0 It seems the time has come to put DEP 0008 into practice and "run Black on the entire Django code repository and make a single commit". Ciao, Paolo On Wed, Oct 20, 2021 at 10:52 PM Paolo Melchiorre wrote: > > On Wed, Oct 20, 2021, 21:51 Mariusz Felisiak > wrote: >> >> >>> I was thinking we can start right now using black in a branch and see which >>> issue will show up and start fixing them. >> >> >> We don't want to merge multiple commits related to black. According to the >> "Implementation" section in DEP 0008, we're going to run Black on the entire >> Django code repository and make a single commit. Running black should not >> encounter any issues … > > > Okay, I also hope the migration to Black will be this smooth. > > So now we just have to wait for 2022. > > Ciao, > Paolo > > -- Paolo Melchiorre https://www.paulox.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/CAKFO%2Bx6dZAw7ftsGvJOV5crHazXLW4RST_t26JDHFcqA1uNXEA%40mail.gmail.com.
Re: Preparing Django code for the Black stable release
That's wonderful news. Thanks for the info, Paolo! Cheers, Markus On Sat, Jan 29, 2022, at 10:24 PM, Paolo Melchiorre wrote: > Hi all, > > Black 22.1.0 has just been released > https://github.com/psf/black/releases/tag/22.1.0 > > It seems the time has come to put DEP 0008 into practice and "run > Black on the entire Django code repository and make a single commit". > > Ciao, > Paolo > > On Wed, Oct 20, 2021 at 10:52 PM Paolo Melchiorre > wrote: >> >> On Wed, Oct 20, 2021, 21:51 Mariusz Felisiak >> wrote: >>> >>> I was thinking we can start right now using black in a branch and see which issue will show up and start fixing them. >>> >>> >>> We don't want to merge multiple commits related to black. According to the >>> "Implementation" section in DEP 0008, we're going to run Black on the >>> entire Django code repository and make a single commit. Running black >>> should not encounter any issues … >> >> >> Okay, I also hope the migration to Black will be this smooth. >> >> So now we just have to wait for 2022. >> >> Ciao, >> Paolo >> >> > > > -- > Paolo Melchiorre > > https://www.paulox.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/CAKFO%2Bx6dZAw7ftsGvJOV5crHazXLW4RST_t26JDHFcqA1uNXEA%40mail.gmail.com. -- 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/18da12b4-75f0-4f48-a9e5-1fbde5caa0e6%40beta.fastmail.com.
Proposal on how add configuration options to Email Backends
This proposal attempts to address the following issues:
https://code.djangoproject.com/ticket/6989 (14 years old)
https://github.com/django/django/pull/13728
and
https://code.djangoproject.com/ticket/31885
https://github.com/django/django/pull/13305
Currently all the parameters to configure the email backend are located
in the global namespace, typically starting with EMAIL_...
This in the past led to discussions whenever a new configuration parameter
was required, because it added another entry to the yet too long list of
configuration
settings.
Since Django allows us to use more than one email backend concurrently,
why don't we configure them in a similar way as we already do it with
database, caching or template engine backends?
Such a configuration setting then may look like:
EMAIL = [
{
'BACKEND': 'django.core.mail.backends.smtp.EmailBackend',
'HOST': 'smtp.example.org',
'HOST_USER': 'smtp_user',
'HOST_PASSWORD': 'smtp_secret',
'PORT': 25,
'FQDN': 'example.org',
# all other related directives
}
]
This would allow each email backend to "bring" its own configuration
settings
contained in their own dictionary. Adding extra settings to this dict will
certainly
lead to less discussions as we currently have.
Personally, I would prefer SMTP = {...} as the main configuration
directive, but EMAIL seems to be more popular in Django.
This would mean that the configuration directives starting from here
will
have
to be replaced, by their counterparts as explained before.
--
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/73f2e1b5-48c7-4331-9041-d6537cda6b7cn%40googlegroups.com.
Re: Proposal on how add configuration options to Email Backends
The idea was pursued in https://code.djangoproject.com/ticket/22734 but
ultimately abandoned.
On Saturday, January 29, 2022 at 6:01:30 PM UTC-5 jacob...@gmail.com wrote:
> This proposal attempts to address the following issues:
> https://code.djangoproject.com/ticket/6989 (14 years old)
> https://github.com/django/django/pull/13728
> and
> https://code.djangoproject.com/ticket/31885
> https://github.com/django/django/pull/13305
>
> Currently all the parameters to configure the email backend are located
> in the global namespace, typically starting with EMAIL_...
> This in the past led to discussions whenever a new configuration parameter
> was required, because it added another entry to the yet too long list of
> configuration
> settings.
>
> Since Django allows us to use more than one email backend concurrently,
> why don't we configure them in a similar way as we already do it with
> database, caching or template engine backends?
>
> Such a configuration setting then may look like:
>
> EMAIL = [
> {
> 'BACKEND': 'django.core.mail.backends.smtp.EmailBackend',
> 'HOST': 'smtp.example.org',
> 'HOST_USER': 'smtp_user',
> 'HOST_PASSWORD': 'smtp_secret',
> 'PORT': 25,
> 'FQDN': 'example.org',
> # all other related directives
> }
> ]
>
> This would allow each email backend to "bring" its own configuration
> settings
> contained in their own dictionary. Adding extra settings to this dict will
> certainly
> lead to less discussions as we currently have.
>
> Personally, I would prefer SMTP = {...} as the main configuration
> directive, but EMAIL seems to be more popular in Django.
>
> This would mean that the configuration directives starting from here
> will
> have
> to be replaced, by their counterparts as explained before.
>
>
--
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/f124b879-4913-42ab-a635-ed3c570e7a83n%40googlegroups.com.
