Earlier quoted context omitted.
Seriously though, why would a company want to start a months long project of moving from python 2 to 3, when their current setup works perfectly, and the project involves the horrifying boring chore of going through every single line of code and making simple changes, and hope that their tests still works, there are no edge cases that crop up due to minor changes in the new version, etc., etc., etc. Seems much more s…
Well, because you're developing against an unsupported runtime. No bug or security updates. If that's fine for you, feel free, otherwise get with the (supported) program. If it's a new project, there are no excuses imho
Lahja – A generic event bus implementation written in Python
71–74 of 74 posts
Re: Lahja – A generic event bus implementation written in Python
#72Earlier quoted context omitted.
> Not all of us move fast and break things here, unlike the web dev world. I had to roll my eyes at that one. Fine if your industry is accepting the high risk of using deprecated releases for new software, but don't try to act like upgrading from deprecated software is "moving fast and breaking things". This deprecation has been announced for 6 years . Python 3 was released over a decade ago. This ain't a new JavaScr…
Another option is of course to use tools that take backward compatibility seriously.
I'm just pointing out that it's a risky move to adopt a soon-to-be-deprecated programming language for new projects, given the potential for security issues that won't be patched. It's the kind of ignorant arrogance that has always bugged me about many companies with non-technical management (please note: these words are not directed at user kgrave given that this appears an edict from above at his company, and he's unable to change it).
Re: Lahja – A generic event bus implementation written in Python
#73Re: Lahja – A generic event bus implementation written in Python
#74Any chance the name is a play on words from the Estonian word "Lahja" as in light-weight?