41–50 of 74 posts
Like Lahja this too is rather much in the alpha stage, but I have been using it in production for over a year now.
I mention it here in case it is interesting to anyone, interest/feedback always welcome!
Earlier quoted context omitted.
Does your industry still use Windows XP/Vista, or PHP4, or Ruby 1.8.7, or Apache 1.x, or MySQL 4.1 or RHEL 5? Those are roughly equivalent era.
Python 2.7 is still maintained, and the last version came out in March IIRC, so there's that. Lots of big players still use Python 2 (Google being the most prominent), and untold smaller players. Besides, Windows XP and PHP are also in use, as are 50+ year old COBOL systems, so there's that. Unless you come in and do the port yourself, many systems are not getting ported anytime soon. RedHat and co will continue to r…
Also Google have golang, which I'd imagine would be their target now, not python 3 (for migrations)
Earlier quoted context omitted.
Does your industry still use Windows XP/Vista, or PHP4, or Ruby 1.8.7, or Apache 1.x, or MySQL 4.1 or RHEL 5? Those are roughly equivalent era.
Python 2.7 is still maintained, and the last version came out in March IIRC, so there's that. Lots of big players still use Python 2 (Google being the most prominent), and untold smaller players. Besides, Windows XP and PHP are also in use, as are 50+ year old COBOL systems, so there's that. Unless you come in and do the port yourself, many systems are not getting ported anytime soon. RedHat and co will continue to r…
Love to try this out some day, a shame that this isn't in Python 2. EDIT: Thanks HN, try working in an industry where every new project is in Python 2, and have no intention to move on, before saying "moeve to 3", it doesn't help at all.
For anyone interested, this is the VFX industry reference platform, which is finally hoping to move to Python 3 next year: https://vfxplatform.com/
what is the usecase for something like this versus celery/rq ?
I suspect the answer will also apply to something like Lahja.
Earlier quoted context omitted.
> Oh please. The EOL on python2 has been massively pre announced. Nope, not when new versions of software comes out with Python 2 still, (can't do anything about those licences bought) small studios cannot afford moving/rewriting tools in P2 to 3, not a priority, rather keep P2.
Can you name some of this software?
Earlier quoted context omitted.
Totally agree, but unfortunately, when you're in a slow moving industry you don't have the luxury of doing rewrites on a whim. You'd be surprised how Python 2 is _still_ being used in this day and age.
OK, but please just tell your bosses that their poor decisions to build new software in Python 2 will put your companies at risk of security exploits for the lifetime of the new software you're building in Python 2. I can almost understand if you have legacy software that your bosses don't want to move to Python 3, but actually building new software in Python 2? It's just crazy and asking for serious problems in the…
Yes, sadly this still happens.
Earlier quoted context omitted.
Tell that to the industry I work in (Games, Movies & VFX) where most of the tools & 3D software scripting are still in Python 2. Not all of us move fast and break things here, unlike the web dev world.
> 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…