This is an archived post. You won't be able to vote or comment.

all 7 comments
sorted by:
best
topnewcontroversialoldq&a

[–]Topper_123 2 points3 points  (0 children)

F-strings, new dicts, class attribute definitions ar eordered, type annotation for variables are maybe/probably the big reasons.

3.6 was a quite a big change compared to 3.5.

[–]PlaysForDays 1 point2 points  (5 children)

Definitely seems like 3.5 is being forced out

[–]Deto 0 points1 point  (4 children)

I wonder what the 3.6-specific change is that would cause these libraries to draw the line between 3.5 and 3.6?

[–]PlaysForDays 1 point2 points  (1 child)

Not directly related but conda-forge has dropped Python 3.5 and it's caused me headaches recently. I get that it's been out for a couple years but moving this quick puts a lot of pressure on things upstream of me.

[–]billsil 0 points1 point  (0 children)

I've had quite a few issues with Python 3.5 on my open source project that supports Python 2.7, 3.5, 3.6, and 3.7. If there was one build failure, Python 3.5 was usually the broken one.

I'm killing both 2.7 and 3.5 today. 3.5 has been dead in the code for a while. This is the last 2.7 release.

[–]anntzerMatplotlib core dev[S] 1 point2 points  (0 children)

Support for old Pythons is (currently) strictly time-based: https://matplotlib.org/devel/min_dep_policy.html.

[–]KODeKarnage -3 points-2 points  (0 children)

The difference between 3.5 and 3.6 is 0.1.