Re: No 'Content-Type' header in response

Don't worry about the unrelated failures, hopefully we'll get that other PR merged soon. On Tuesday, December 27, 2016 at 12:01:36 AM UTC-5, roboslone wrote: > > Okay, so I've submitted a pull-request > resolving this issue. But > tests for timesince

Django 2.0 Python version support (Python 3.6+ only?)

When I drafted the 1.11 release notes in May, I wrote, "The next major release, Django 2.0, will only support Python 3.5+." Our Python version support policy is "Typically, we will support a Python version up to and including the first Django LTS release whose security support ends after securi

Re: Considering removing support for ("iLmsu") regex groups in URLpatterns. Do you use them?

I created a ticket and pull request for the deprecation: https://code.djangoproject.com/ticket/27648 https://github.com/django/django/pull/7749 On Friday, December 23, 2016 at 10:22:40 AM UTC-5, Tim Graham wrote: > > I found a flask thread [0] where Armin Ronacher said this about > case-insensit

Re: Should SECRET_KEY be allowed to be bytes?

Thanks Aymeric. How about this documentation addition: Uses of the key shouldn't assume that it's text or bytes. Every use should go through :func:`~django.utils.encoding.force_text` or :func:`~django.utils.encoding.force_bytes` to convert it to the desired type. https://github.com/django/dja

Adding custom attributes to Django sitemaps framework

Hi, I am not sure if this has been discussed before or not. I think adding a custom attribute to sitemap template would a nice thing to do. As of now the https://github.com/django/django/tree/stable/1.10.x/django/contrib/sitemaps/templates template has http://www.sitemaps.org/schemas/sitema

Re: Django 2.0 Python version support (Python 3.6+ only?)

Imo we should not drop Python versions overeagerly. After all I do not wanna compile our own python for djangoproject.com :D Given that Redhat is on Python 3.4 for the foreseeable future, I'd actually even like to see 3.4 still supported in Django 2.0 unless there is a good reason to drop it. F

Re: Django 2.0 Python version support (Python 3.6+ only?)

Collin raised a fair point in #django-dev that Ubuntu 16.04 bundles Python 3.5. I guess 16.10 will include Python 3.6 -- that will be released before Django 2.0 in December 2017. Presumably any Python's we don't drop for 2.0 we will have to support until the next LTS (which means 2 more years w

Re: Adding custom attributes to Django sitemaps framework

I don't have a lot of experience with sitemaps so at least for me, it would be nice to see some proposed code changes to understand the idea a bit better. From my naive point of view, it looks like you need a custom template to output anyway? On Tuesday, December 27, 2016 at 2:37:20 PM UTC-5,

Re: Django 2.0 Python version support (Python 3.6+ only?)

I won't mind dropping support for Python versions that are not supported up to the end of the support period of the next LTS (2.2 in this case). If you want to use long-term stability and/or support for current Python versions, you should use the current django LTS version, which will be 1.11. I am

Re: Django 2.0 Python version support (Python 3.6+ only?)

Yes, Django 1.11 is the last version to support Python 2.7. This is documented in the 1.11 release notes, in https://www.djangoproject.com/download/#supported-versions, and elsewhere. On Tuesday, December 27, 2016 at 4:37:06 PM UTC-5, MMeent wrote: > > I won't mind dropping support for Python v

Re: Django 2.0 Python version support (Python 3.6+ only?)

On Tue, Dec 27, 2016 at 3:52 PM Tim Graham wrote: > Collin raised a fair point in #django-dev that Ubuntu 16.04 bundles Python > 3.5. I guess 16.10 will include Python 3.6 -- that will be released before > Django 2.0 in December 2017. > > Presumably any Python's we don't drop for 2.0 we will have

Re: Django 2.0 Python version support (Python 3.6+ only?)

I'm okay with keeping Python 3.5 support around. I agree it would be a bit impractical to release Django 2.0 in December without being able to run it on the most recent Ubuntu LTS. If we dropped Python 3.5 support after Django 2.1 that would give Django (2.1) support until December 2019 (or Apr