Live data from Hacker News

Lahja – A generic event bus implementation written in Python

github.com

31–40 of 74 posts

Re: Lahja – A generic event bus implementation written in Python

#31
post #15
post #10

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. Then how many more years do they need to switch to Python3?

What if they don't want to switch to anything they aren't absolutely forced to, and otherwise 2.x works for them, period?

How many years does it take companies to switch from COBOL (which still runs billions of lines of 40+ years critical code)?

Re: Lahja – A generic event bus implementation written in Python

#32
post #14
post #9

Earlier quoted context omitted.

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.

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 very near future.

Re: Lahja – A generic event bus implementation written in Python

#33

what 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.

Well, it technically does (through its invocations of billiard, it's multiprocessing fork), but it's pretty ad hoc and not exposed for much user control. So you're basically right, I'm just being pedantic.

Re: Lahja – A generic event bus implementation written in Python

#34

Earlier quoted context omitted.

AFAIK, celery doesn't provide a message passing bus between main process and sub-processes.

Well, it technically does (through its invocations of billiard, it's multiprocessing fork), but it's pretty ad hoc and not exposed for much user control. So you're basically right, I'm just being pedantic.

Yes ok initial parameter passing and gathering results may be considered a message bus. I was going to mention that, but I got lazy.

Re: Lahja – A generic event bus implementation written in Python

#35
post #6

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.

https://pythonclock.org/ - 5 Months and 2 days to go. Do not do any new projects in Python 2. There is no technical reason for you to do so. If management is an issue, show them the facts.

Also, Python 3.9 is now out which means there's been more than enough time to migrate - https://docs.python.org/3.9/whatsnew/3.9.html

Re: Lahja – A generic event bus implementation written in Python

#36
post #21

Earlier quoted context omitted.

> Then complain to the companies you license software from for continuing to build on a soft-deprecated platform. You think we haven't been doing this? We had a representative from one of these vendors come in to discuss their roadmap, they told us straight up that "We still intend to keep using Python 2". > Don't complain to developers for ignoring a platform whose deprecation was announced over a decade ago. Yes, b…

> Yes, because web dev is the hot tech stuff now, nobody wants to work in a boring sector, so they are not willing to change anything, cycle continues. Change what? You're asking for...what exactly? People to provide support for a deprecated platform? That just encourages those companies you're complaining about to continue to use python2 and further splits the ecosystem. No!

> Change what? You're asking for...what exactly? People to provide support for a deprecated platform?

Instead of trying to put words in my mouth and being hostile, try to address my concerns. What I mean is that nobody that is a dev wants to work in a slow boring sector, Which means no work gets done to Python 3 on the vendor side hence, studios like ours keep developing on it.

Nothing changes and no choice other than leaving.

Re: Lahja – A generic event bus implementation written in Python

#38
post #6

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.

What industry is it, might I ask (so I can know to avoid it)?

If you say airline...

Re: Lahja – A generic event bus implementation written in Python

#39
post #6

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.

https://pythonclock.org/ - 5 Months and 2 days to go. Do not do any new projects in Python 2. There is no technical reason for you to do so. If management is an issue, show them the facts. Also, Python 3.9 is now out which means there's been more than enough time to migrate - https://docs.python.org/3.9/whatsnew/3.9.html

3.8 won't be released until late October (https://www.python.org/dev/peps/pep-0569/). 3.9 is a ways off.

Re: Lahja – A generic event bus implementation written in Python

#40

Earlier quoted context omitted.

https://pythonclock.org/ - 5 Months and 2 days to go. Do not do any new projects in Python 2. There is no technical reason for you to do so. If management is an issue, show them the facts. Also, Python 3.9 is now out which means there's been more than enough time to migrate - https://docs.python.org/3.9/whatsnew/3.9.html

3.8 won't be released until late October ( https://www.python.org/dev/peps/pep-0569/ ). 3.9 is a ways off.

Sorry, should have stated it's a pre-release.
Post reply on HN