Closed ivanistheone closed 7 years ago
@nvbn any chance to get this merged?
+1
+1
I guess the devs do not want the coverage to decrease
+1 works for me
I think that optparse can be dropped together with support for Django < 1.8 (the switch to argparse was on 1.8+)...
@yprez the thing is Django 1.7 is a "long term release" and is the version that comes with many distrors (e.g. Debian), so might as well keep the support.
@ivanistheone I'm pretty sure that 1.8 is the LTS, and 1.7 is no longer supported...
here: https://www.djangoproject.com/s/img/release-roadmap.e844db08610e.png
and if you switch doc to 1.7 at the top of page appear warning about not supported version
Okay. I'll be happy to update the PR if the project maintainers agree with dropping Django 1.4 and 1.7 from the supported list (and the test suite).
Maintainer seem busier with other important matters... (https://github.com/nvbn/thefuck) Not too happy about that, I'm looking for applying patch during deployment.
Thanks!
Thanks to you! My post was a little bit provocative, but I'm happy to leave my patch fade away...
@nvbn thanks! a new release perhaps?
@yprez released as 5.2.0 😊
test_out
Note this pull requests supersedes #66 #67 by @freeyoung (leaving the old code in place allows us to support Django 1.7 and Django 1.10+)