`pip install Django` gives the latest version of Django that's compatible 
for the current version of Python. Yes, users will have to switch versions 
at docs.djangoproject.com and they'll be in the same situation at 
docs.python.org if they're using Python 3.5. For learning Django, I'd think 
the latest LTS should be just fine. I get the sense that many intro to 
Django books are  updated at each LTS release.

At this point, I don't see much consensus so I think the default course of 
action would be to stick with the current policy unless someone wants to 
ask the technical board to vote upon the new proposal.

For what it's worth, there's a new test failure after a recent patch due to 
non-deterministic dict ordering in Python 3.5 which demonstrates the sort 
of minor annoyances that take time away from making useful improvements to 

On Thursday, January 24, 2019 at 3:33:33 PM UTC-5, Carlton Gibson wrote:
> To be honest, I'm surprised there's even one person who comes within a 
> 1000 miles of this list who's using Python 3.5. :)
> My reason for thinking we should follow Python's supported versions is 
> users, and particularly beginning users, who have got they-don't-know 
> version and find a tutorial just what... no sorry need... `pip3 install 
> Django` to work, and give them the version of Django that corresponds to 
> what they see when they visit docs.djangoproject.com. 
> I don't agree this is theoretical at all. 
> It's not just Debian. (Which doesn't fit my mental model here really...)
> It's all those few-years-old computers out there. 
> It's for example Raspbian, which as of this month is still shipping Python 
> 3.5. 
> So my boy, who's 10, says, 
> - What would you use? 
> - Well I'd use Django (obviously) 
> - Can I use that?
> - Yeah... 
> If we do drop Python 3.5 I have to say, "Well, no. But you can use this 
> old one." That's not as cool.
> But there will be people who are more seriously affected. 
> > Who is saying, "I want to use the latest version of Django, but I want 
> to use a really old version of Python."
> No one is saying this. The notion of versions doesn't come into it. We're 
> well beyond the barrier-to-entry before we get there. 
> I (just my opinion on this) think we mistake our audience if we forget 
> this.  
> (For this reason I don't think the deployment issue is the relevant one. 
> It's about people learning to programme, not professionals.) 
> We can't support everything forever, and I'm as keen as anyone to push 
> forward, but following Python is (for me) the thing we should do. 
> I think Django's position in the Python eco-system requires it. 
> Of course if we don't, things are easier for us, yes. 
> Again, just my opinion. 
> C. 

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 post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
For more options, visit https://groups.google.com/d/optout.
          • ... Adam Johnson
          • ... Ryan Hiebert
          • ... Tim Graham
          • ... Ryan Hiebert
          • ... Carlton Gibson
          • ... Tom Forbes
          • ... Dan Davis
          • ... Florian Apolloner
          • ... Tim Graham
          • ... Joe Tennies
          • ... Tim Graham
          • ... Carlton Gibson
          • ... Joe Tennies
          • ... Alex Krupp
          • ... Joe Tennies
          • ... Carlton Gibson
  • R... Joe Tennies
  • R... 'Ivan Anishchuk' via Django developers (Contributions to Django itself)
    • ... Tim Allen

Reply via email to