5 ms·
Why can't your Python 2 services talk to your Python 3 web app?
by BHSPitMonkey 10y ago
Why can't your Python 2 services talk to your Python 3 web app?
- coldtea 10y agoWhy should I maintain code, servers and libs in 2 versions of a backend programming language?
- agildehaus 10y agoBecause one is essentially EOL?
- coldtea 10y agoWell, I'm for user driven EOL, as opposed to top-down, we-know-better EOLining. And the latter doesn't work so well thus far for Python 3.
- parzivalm 10y agoI think you see this argument used a lot when it comes to Python 3 about it not working so well. I don't see the maintainers changing their minds about EOL on python 2 so either switch to Python 3 or to another language. There is so much toxicity around the Python community because of people thinking they are entitled to have everyone still support Python 2.
- TeMPOraL 10y agoIf enough people like Python 2 that much, I guess someone else can take over maintaining and developing this language version past the official EOL date.
- collinmanderson 10y agoLike Guido's employer, for example. (see pyston)
- mike-cardwell 10y agoThen don't. Stick with Python 2 and accept that means you're going to stop getting work done for you for free in 3 years time.
- flukus 10y agoBecause it is and always has been a sensible middle ground between rewriting everything for every release and never upgrading.