Closed igeligel closed 5 years ago
@igeligel I guess since fstrings are supported since Python 3.6, support for Python 3, 3.4 and 3.5 also needs to be dropped, right? Is that really necessary?
The question is if it is really necessary to support Python 3, 3.4 and 3.5 since upgrades will not introduce any breaking changes.
OK then let's drop support for those python versions. Could you update the setup.py then?
Declining this. Readme updates were done in separate PR. Django 1.11 still supports Python 2 till 2020. It's not in the way right now, and there's no up side just for format strings. Feel free to rebase and reopen when you're adamant about it.
Just an unpopular opinion:
Maybe break the things so enterprises are forced to upgrade their applications and if they cannot or do not want to do it, they need to invest in the engineering department of the company. If this is not supposed to happen it seem that other things are more important than engineering and the company has to live with the disadvantages of using an old version. If you still do not want to invest the money, the company might have other problems like a not well-running product, at least it is not generating enough profits.
What kind of change does this PR introduce?
Does this PR introduce a breaking change?
Review and Merge
Who
When
Other information