You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Christian. I hear your concerns, but python 3 was released nearly a decade ago. It has been the preferred environment for new development for nearly as long. Libraries that are still holding out and not supporting 3.x are few and far between (and generally unmaintained). Do you have any particular libraries that you consider critical that still don't support python 3?
Regretfully, I don't plan to put in this sort of work either way. There's too many other things to do rather than supporting some dusty old dinosaurs. I'd also not be interested in merging a change that supports decade-old python unless it's clear to me that it won't introduce a substantial maintenance headache for the rest of us non-laggards.
Generally, I think it is bad behavior to keep supporting 2.7 with libraries when support for 2.7 was supposed to be dropped from cPython a year ago. There are some libraries I maintain where we do this for necessity (e.g. https://github.com/halfak/MediaWiki-OAuth). I don't see that with this library. It's good that we encourage progress. Maybe I can convince you to come over to python 3 land instead. I bet that'll take fewer man-months than supporting 2.7.
Many libraries and framework currently support only python2. Backporting this library could be helpful.
Thank you.
The text was updated successfully, but these errors were encountered: