--
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 post to this group, send email to django-d...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/ce5f3cdb-a623-4bcc-a661-bf88d91a5a7f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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 post to this group, send email to django-d...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/85adb894-c908-4835-98fe-96c859d79a15%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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 post to this group, send email to django-d...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/51dfc517-8b5a-4803-9f8d-daa1bf920e7b%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAFO84S5kx5W18xA7H99cJk9%2B7s4LVRNJCD7RDfaXBz76HjEAQQ%40mail.gmail.com.
Don't discount being able to use features from newer versions of python within Django itself.- dicts are more performant
- dicts/kwargs/class attributes are ordered (cpython implementation detail for 3.6 - allowing us to consider removing descriptor counters)
- fstrings
- type annotations (something some people are quite in favour of)
- async comprehensions and generators (less important for Django right now - may be more important for Channels)
- secrets module
- pathlib
- descriptor improvements (set_name, __init_subclass__)
I'm more in favour of maintaining the existing policy than playing favourites with distro support, but not strongly so. The LTS Django is already covering Python 3.5 for 18 months **longer** than the EOL. I don't think the newest versions of Django need to be so concerned with distro compatibility.
I worry about the precedent we'd set if we made an exception for Debian, because the next question would be "OK, can we have an exception for Red Hat, too?" Keep in mind Red Hat currently sells up to fourteen years of support for their RHEL platform.
So, phrasing... maybe... as a draft: "Typically, we will support a Python version unless it will be end of life before the corresponding version of Django is outside of mainstream support. For example, Python 3.5 security support ends September 2019, whilst Django 3.1 ends mainstream support in April 2021. Therefore Django 3.0, which is end of life August 2019 is the last version to support Python 3.5."
Sorry I mistyped. " Python 3.5 security support ends September 2020" (but you get the point.)
--
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 post to this group, send email to django-d...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/ac50c67c-51a8-4c94-9505-c19fc6fd7cfc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
So, phrasing... maybe... as a draft: "Typically, we will support a Python version unless it will be end of life before the corresponding version of Django is outside of mainstream support. For example, Python 3.5 security support ends September 2019, whilst Django 3.1 ends mainstream support in April 2021. Therefore Django 3.0, which is end of life August 2019 is the last version to support Python 3.5."+1. A subtle change on the existing policy but it makes a difference.
Let's hear from people who find the current Python support policy insufficient for their needs.
--
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 post to this group, send email to django-d...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/19e099cf-6087-4efd-9138-d338f12bbf2c%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAFNZOJPdaWYJ9LCPZsG9dE66ka%2B8M_8Y4_%2BzMwFNz4er1pXi8w%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/c25bb851-f334-48d4-bdd4-470c0ff10e2c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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 post to this group, send email to django-d...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/2c23caa4-b83a-4e45-9811-a62af2b4c311%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
The biggest issues with beginners I see at events like Django Girls or just regular Python meetups involve people needing to edit their .bash_profile or .bashrc files. Most people can figure out how to download the right version of Python for their platform, but then their shell to actually use that version of Python is where things go sideways. Same thing with setting the DJANGO_SETTINGS_MODULE.
The basic issues are:- Figuring out which version of python3 your interpreter is using (and even knowing you need to know that)
- Knowing how to open the appropriate shell settings file, add the right line in the right place, and save it. (Especially since if there is already stuff there, beginners aren't going to have any idea what any of it is doing which only adds to the confusion.)
- Knowing they need to open a new terminal window or source the settings file.- Knowing how to read the error message if something went wrong, and the fix whatever the problem is.
- Knowing how to actually install Django... E.g. pip vs pip3, to sudo or not to sudo, etc.
- Knowing what version of Django to install. E.g. beginners mostly aren't going to know what LTS stands for or understand the implications of that.
For beginners, just getting to the point where running the development server doesn't throw an error is probably harder than the rest of the tutorial combined. So I think making it as easy as possible for beginners is a real issue that should be prioritized. As an anecdote, the only reason why Reddit is built on Postgres instead of MySQL is that they couldn't figure out how to get MySQL installed and running.That being said, my understanding is that there are a bunch of API changes to Python's async modules between Python 3.5 and 3.6, and I know having async functionality in Django is a big deal for a lot of people. If there's money to pay people to work on that full time then it doesn't matter as much, but if there isn't then I'm assuming a lot of that work will probably get pushed back a year to when it'll at least be less work, which is potentially problematic if it's already going to be a multiyear project as is.While async itself doesn't especially impact me at this point, obviously everyone benefits from having smart people in the larger Python/Django community to create and maintain the packages we all depend on, and I worry about losing folks to node or golang.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/c948baf5-91a2-4577-aeaa-89735bb2e444%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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 post to this group, send email to django-d...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/a8e5bc63-15b1-4c77-92ae-59e61daa30fd%40googlegroups.com.