Hacker News Reader

Comment by coldtea | Hacker News Reader

Well, if one wants stability and production releases, why would they be trying a new, experimental, JIT compiler for Python?

View on HN

If it just required doing "pip install" then I'd try it to see how fast my test suite runs. But since it only works with Python 3.10 and .NET 6, realistically even just spending five minutes messing with it will require first waiting 18 months or whatever.

Seems like it would take no more than 5 minutes to download and untar the listed dependencies, though. I don’t understand this attitude about experimentation.

I might mess up my computer!!

some people are helpless without their package manager and the maintainers that tell them what software that can run

You can even neatly do it in a docker container that you throw away after if you don't want to mess up anything locally.

Haha that's the rabbit hole. Two weeks later you're compiling your own kernel from sources just to be able to get that specific version of libc so that you can get libfoo working so that you can get libbar working so that you can get... You get the idea.

been there, done that, got the tshirt and worthless equity ;)

these days, just spin up some disposable container/vm and tinker...

> waiting 18 months or whatever

Seems like a problem with however your system distributes software, not with Pyjion.

What does it take 18 months to do?

Well for one I can't run Python 3.10 in production because I use AWS Elastic Beanstalk, which currently only supports 3.8. And my development environment is Ubuntu, which also doesn't support it out of the box. So short of scheduling two weeks to retool both my production and local development environments, which I'm not going to do because it would be a complete waste of time, there is zero benefit to me to even looking into this.

Right, but those are you-problems. You use a way to get dependencies that's very slow. That's not a Pyjion problem.

> That's not a Pyjion problem.

I wasn't criticizing Pyjion, I was responding to coldtea's comment saying that people who can't run this in production would likely not be interested in trying it. I have zero issue with Pyjion, and I'm also happy with my production setup as is.

>Well for one I can't run Python 3.10 in production because I use AWS Elastic Beanstalk

And why wouldn't you want to try this in production in the first place?

Check out pyenv, you can run whatever versions of python you want to without messing with the system or other virtualenvs.

Reply on news.ycombinator.com