Hacker News new | past | comments | ask | show | jobs | submit | zatarc's comments login

I think the is_computer_on_fire function is far more useful

Pyjion requires: CPython 3.10 and .NET 6

.NET 6 Release: 19 hours ago (https://github.com/dotnet/core/blob/main/release-notes/6.0/6...)

... ok.


We found the Arch Linux developer XD "All hail rolling releases, why haven't you updated yet? I published it 15 minutes ago!"


haha :)


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


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.


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


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.


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


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


>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?


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.


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


.NET 6 has been in prerelease for a while, and it's the next LTS release. Makes sense that it would be used as soon as it was available. Upgrading from 5 to 6 should be pretty trivial.


I've tried it on Fedora:

https://docs.microsoft.com/en-us/dotnet/core/install/linux-f...

> The latest version of .NET that's available in the default package repositories for Fedora is .NET 5. Installing .NET 6 through the default package repositories is coming soon. For now, you'll need to install .NET 6 in one of the following ways:

> Install the .NET SDK or the .NET Runtime with Snap.

> Install the .NET SDK or the .NET Runtime with a script.

> Install the .NET SDK or the .NET Runtime manually.

Nope, thank you


.NET 6 was just released this morning, so I'd assume it will take at least a little bit of time to get into the default package repositories.


Thats the point.


Pyjion 1.0 was released yesterday, so that checks out? :)


Step 1: Avoid AWS.


This was my first thought. Understand that it's a financial risk to work with AWS at both small and large scale.

I have a personal AWS setup that has no costs, at this time. I've run a business account at 50k+/mo. I've never had an account suspended or lost my credentials and those stories scare me a bit.


After trying to set up Fargate and it only sending my logs to cloudwatch 25% of the time (Id deploy and get no logs, try again two to three times literally just clicking the button in the web console again and then it would work), if course AWS charged me for every . Two days and a $150 bill later I got fed up and moved to DigitalOcean App platform, where I fixed the issue (was a bug in my health checks) within ten minutes and a monthly bill of $10. That day I decided I will never again use AWS unless I can pay someone who really knows what they’re doing to do it for me (and I have a good reason to actually want to use AWS). My life has been much less stressful since.


Germany: hold my beer! 1.78€ or $2.09

But thats not point here. Everyone is talking about the climate change and then we want to charge millions or billions of phones with ~50% extra power?

Good idea!


In absolute terms it's nothing though. An average household uses 4000 kWh of electricity in the UK (less than half of the average us household), so saving the 5kWh on 4 phones is a 0.5% saving, which is roughly equivalent to running your home boiler for 10 minutes per year. Turning off your thermostat for one evening would have the equivalent impact of not using a wireless charger for a century.


> In absolute terms it's nothing though.

Symbols can hold power though.


Do we not have enough symbols? Plastic bags, domestic recycling, plastic straws are all strong "symbols" and yet we're still fighting about a couple of kWh rather than making any meaningful change.


Sure, as long as the electricity doesn't come from fossil fuels. Why not?


You can avoid unwanted agents by avoiding cloud provider.


Try Parsel: https://github.com/scrapy/parsel

It's way faster and has better support for CSS selectors.



Just use (feature-)branches.

You can commit every single character if you in the mood. At the end, when your new feature is complete, you just squash all commits in this branch to one single commit ("add feature xyz") and merge/rebase it to your main dev branch.

Now it is really easy to identify the actual code behind a new feature.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: