Re: Django Version 3.2 Roadmap

2020-05-13 Thread Carlton Gibson 
I’d probably just push it for the 6th in this case, after the weekend.

(I obviously live a sheltered life: April fools never occurred to me... )

On Thu, 14 May 2020 at 00:02, Florian Apolloner 
wrote:

> On Wednesday, May 13, 2020 at 4:40:55 PM UTC+2, Adam Johnson wrote:
>>
>> This looks good to me, it fits the preset release cadence. Although the
>> final release will be on "April fools day," it's something we've done
>> several times before.
>>
>
> While we might have done it (did we actually do that several times
> before?), I'd like to suggest moving it  to April 10th. (or whatever suits
> us). Every year the first of April seems to be a high tension day, if there
> is no necessity to release on such a day I'd strongly recommend against it.
> It is just easier on the brain if you read a news article and you don't
> have to decide if it is a possible prank simply because it is fools day. I
> realize that you cannot trust news any other day either, by why pile onto
> that if you don't have a reason…
>
> --
> 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/f9e3c147-06d8-4b3d-a250-cd3a8d00af90%40googlegroups.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/CAJwKpyTNoLFojY%2BGyaTta6FqPkAA40nK48BFJW--SwCoiyX19A%40mail.gmail.com.

Re: Django Version 3.2 Roadmap

2020-05-13 Thread Florian Apolloner 
On Wednesday, May 13, 2020 at 4:40:55 PM UTC+2, Adam Johnson wrote:
>
> This looks good to me, it fits the preset release cadence. Although the 
> final release will be on "April fools day," it's something we've done 
> several times before.
>

While we might have done it (did we actually do that several times 
before?), I'd like to suggest moving it  to April 10th. (or whatever suits 
us). Every year the first of April seems to be a high tension day, if there 
is no necessity to release on such a day I'd strongly recommend against it. 
It is just easier on the brain if you read a news article and you don't 
have to decide if it is a possible prank simply because it is fools day. I 
realize that you cannot trust news any other day either, by why pile onto 
that if you don't have a reason…

-- 
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/f9e3c147-06d8-4b3d-a250-cd3a8d00af90%40googlegroups.com.

Proposal: django project name

2020-05-13 Thread Christian González 
Hi all,

I didn't find anything about that in the archive here, so I'd like to
come to you with an idea which is either very dumb (please tell me) or I
don't know why anyone hasn't thought about it...

I'm starting a bigger project with a self-created plugin system (GDAPS,
alrady mentioned). Working nicely, but I came across a few Django
shortcomings which are sometimes easy to workaround, but could be done
better: the django project name.

TL;DR: Django has no (builtin/explicit) settings variable like
PROJECT_NAME. Should have.

Long version:

If you have (like in my case) an application which is more than a single
django app, and could have various 3rd party additions/plugins, there is
no common sense of retrieving the overall "name" of the application. If
you create a project using django-admin startproject myproject - the
name says it, you name the project. It is written into various places,
mostly comments etc.:

foo/asgi.py:ASGI config for foo project.
foo/asgi.py:os.environ.setdefault('DJANGO_SETTINGS_MODULE',
'foo.settings')
foo/settings.py:Django settings for foo project.
foo/settings.py:ROOT_URLCONF = 'foo.urls'
foo/settings.py:WSGI_APPLICATION = 'foo.wsgi.application'
foo/urls.py:"""foo URL Configuration
foo/wsgi.py:WSGI config for foo project.
foo/wsgi.py:os.environ.setdefault('DJANGO_SETTINGS_MODULE',
'foo.settings')
manage.py:    os.environ.setdefault('DJANGO_SETTINGS_MODULE',
'foo.settings')

But foo is no variable. Needers of this inofficial project name use
workarounds like settings.ROOT_URLCONF[0] to get that name. But that's
always a bit of a whacky feeling when I do it - doesn't seem like - "I'm
sure this will be supported for the next 20 years".

When it comes to frontends, it's worse. In my case, my GDAPS module
enables a Vue.js frontend, which needs a index.html which loads Vue.
This file is (in SPA apps) the only file which is rendered using Django
templates. No problem, put in gdaps' templates directory and go. Works
fine, as long as the user of GDAPS is fine with my shipped index.html
and the corresponding pre-defined url path that renders that index file
using TemplateView.

If he wants to override that file using his own template (with maybe
another font loaded etc.) I first thought I just change GDAPS to
dynamically load the template in GDAPS' urls.py - but therefore it
should know the name of the project it is a part of.

I can do that using a setting named PROJECT_NAME and place a url
definition like

path("",
TemplateView.as_view(template_name=os.path.join(settings.ROOT_URLCONF[0],"index.html")),
name="app")

into urls.py. So the user can place an index.html into foo/templates/foo/ and 
it should work.

But as said, this seems to me as - hey, ROOT_URLCONF[0] - really, this is the 
project name?

path("",
TemplateView.as_view(template_name=os.path.join(settings.PROJECT_NAME,"index.html")),
name="app")

seems better to me.
I first thought that Django could provide that as "builtin" setting, but OTOH, 
explicit is better than implicit,
so why not
a) create a setting (which is created by django-admin createproject along with 
the other parsed templates) named
PROJECT_NAME o DJANGO_PROJECT_NAME
or
b) (because settings are not used in wsgi.py, manage.py etc.) create it earlier 
in the process - or does it have to be written at more than one places?
This would violate DRY.

Please tell me what you think about that.

Yours,
Christian

-- 
Dr. Christian González
https://nerdocs.at

-- 
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/37527e26-4e21-2684-5766-145441c6ae50%40nerdocs.at.


pEpkey.asc
Description: application/pgp-keys

Re: Django Version 3.2 Roadmap

2020-05-13 Thread Markus Holtermann 
Hi Carlton,

thank you. The proposal looks good to me. +1

Cheers,

Markus

On Wed, May 13, 2020, at 2:51 PM, Carlton Gibson wrote:
> Hi all. 
> 
> I've prepared a draft of the Roadmap for Django 3.2 here: 
> 
> https://code.djangoproject.com/wiki/Version3.2Roadmap
> 
> Following the established release cadence, Django 3.2 will be due in 
> April 2021. 
> 
> The key dates are these. 
> 
> `
> = ==
> January 14, 2021 Django 3.2 alpha; feature freeze.
> 
> February 18 Django 3.2 beta; non-release blocking bug fix freeze.
> 
> March 18 Django 3.2 RC 1; translation string freeze.
> 
> April 1 Django 3.2 final
> = ==
> `
> 
> In accordance with DEP 10, I'd like to ask the Technical Board to 
> review this when able, and approve it or suggest adjustments if needed.
> 
> Thanks. 
> 
> 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/d19d3303-34aa-4e87-b867-04e7b48f81a5%40googlegroups.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/78f612d8-58e6-4f46-b371-c079d503f826%40www.fastmail.com.

Re: Django Version 3.2 Roadmap

2020-05-13 Thread Carlton Gibson 


> On 13 May 2020, at 16:40, Adam Johnson  wrote:
> 
> I edited the wiki page slightly to rename "committer" to "merger" in 
> accordance with DEP 10.

Ah, yes. Good catch. 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/78F43917-396C-4FF1-8C92-4FA662D6A412%40gmail.com.

Re: Django Version 3.2 Roadmap

2020-05-13 Thread Adam Johnson 
Hi Carlton

This looks good to me, it fits the preset release cadence. Although the
final release will be on "April fools day," it's something we've done
several times before.

I edited the wiki page slightly to rename "committer" to "merger" in
accordance with DEP 10.

Thanks,

Adam

On Wed, 13 May 2020 at 13:51, Carlton Gibson 
wrote:

> Hi all.
>
> I've prepared a draft of the Roadmap for Django 3.2 here:
>
> https://code.djangoproject.com/wiki/Version3.2Roadmap
>
> Following the established release cadence, Django 3.2 will be due in April
> 2021.
>
> The key dates are these.
>
> =  ==
> January 14, 2021   Django 3.2 alpha; feature freeze.
>
> February 18Django 3.2 beta; non-release blocking bug fix freeze.
>
> March 18   Django 3.2 RC 1; translation string freeze.
>
> April 1Django 3.2 final
> =  ==
>
> In accordance with DEP 10, I'd like to ask the Technical Board to review
> this when able, and approve it or suggest adjustments if needed.
>
> Thanks.
>
> 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/d19d3303-34aa-4e87-b867-04e7b48f81a5%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/CAMyDDM0iTGYPrNexVBqa90Cczm1BAQGD61R4t_cPe%2B0CCqXWAg%40mail.gmail.com.

Django Version 3.2 Roadmap

2020-05-13 Thread Carlton Gibson 
Hi all. 

I've prepared a draft of the Roadmap for Django 3.2 here: 

https://code.djangoproject.com/wiki/Version3.2Roadmap

Following the established release cadence, Django 3.2 will be due in April 
2021. 

The key dates are these. 

=  ==
January 14, 2021   Django 3.2 alpha; feature freeze.

February 18Django 3.2 beta; non-release blocking bug fix freeze.

March 18   Django 3.2 RC 1; translation string freeze.

April 1Django 3.2 final
=  ==

In accordance with DEP 10, I'd like to ask the Technical Board to review 
this when able, and approve it or suggest adjustments if needed.

Thanks. 

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/d19d3303-34aa-4e87-b867-04e7b48f81a5%40googlegroups.com.