what is the usecase for something like this versus celery/rq ?
Lahja – A generic event bus implementation written in Python
11–20 of 74 posts
Re: Lahja – A generic event bus implementation written in Python
#12Earlier quoted context omitted.
Please, please don't use Python 2.
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.
Oh please. The EOL on python2 has been massively pre announced. Games, Movies and VFX can afford the port costs and have a huge liability looming.
There was no "move fast and break things" in this python 3
Re: Lahja – A generic event bus implementation written in Python
#13Earlier 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.
Oh please. The EOL on python2 has been massively pre announced. Games, Movies and VFX can afford the port costs and have a huge liability looming. There was no "move fast and break things" in this python 3
> 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.
Re: Lahja – A generic event bus implementation written in Python
#14Love 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.
Please don't use Python 2 for any software that anyone else will ever have to work with or maintain. Python 2 is very close to being not supported anymore, which means no more security updates, etc.
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.
Re: Lahja – A generic event bus implementation written in Python
#15Earlier quoted context omitted.
Please, please don't use Python 2.
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.
Then how many more years do they need to switch to Python3?
Re: Lahja – A generic event bus implementation written in Python
#16Earlier quoted context omitted.
Oh please. The EOL on python2 has been massively pre announced. Games, Movies and VFX can afford the port costs and have a huge liability looming. There was no "move fast and break things" in this python 3
> 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.
Then complain to the companies you license software from for continuing to build on a soft-deprecated platform. Don't complain to developers for ignoring a platform whose deprecation was announced over a decade ago.
And certainly don't badmouth people who are using the not-deprecated tool as being ok with unstable infra.
Re: Lahja – A generic event bus implementation written in Python
#17Love 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.
Me too but it's not been released in ALGOL 68 either!
Upgrade. Or accept that you are using a dead language.
Re: Lahja – A generic event bus implementation written in Python
#18what is the usecase for something like this versus celery/rq ?
AFAIK, celery doesn't provide a message passing bus between main process and sub-processes.
Re: Lahja – A generic event bus implementation written in Python
#19Love 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.
This library uses asyncio, which is Python3. What do you expect?
You may be okay to stick with Python 2, but this means you also agree not to expect new features and new libraries. So please don't mention Python 2 to a new library.
Re: Lahja – A generic event bus implementation written in Python
#20Love 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.
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.