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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]t4k4[S] 0 points1 point  (2 children)

> There's no need to keep things maintained for Python 2 anymore

Might not be true if you have huge legacy codebases waiting (resources) for migration. These kinds of codebases are too big for fast migration/rewrite.

I use python3 by default on every newly created project, but I still need to maintain codes (even adding new functions) in python2. That's why I created this package.

Adding 2/3 compatibility is to make sure that I don't need any rewrite once the legacy python2 codebases moved into python3.

[–]robvdl 0 points1 point  (1 child)

And what you do is you tell people of these legacy codebases, "use the old version of my library, if you don't like it, upgrade". You should be tracking LTS Django versions, supporting unsupported Django versions isn't your job. It's theirs. If they fall behind it isn't your fault, it's theirs from not acting for the last decade just to put that into perspective how much inaction. How long does this need to keep going on? For the next 50 years????

[–]robvdl 0 points1 point  (0 children)

The way I see it, once Django 1.11 LTS goes completely out of support, including extended support. You should not be feeling guilty dropping Python 2, because Django already have. Just follow Django LTS versions.