You also need to know what the internal GitHub event json looks like. Using act was such a pain I just gave up. Have tried several times now and it’s just easier to create a second repo just for testing and overwrite it with your current repo anytime you need to do major workflow changes.

https://chriswarrick.com/blog/2023/01/15/how-to-improve-python-packaging/

I think you have got to be meme’ing. You literally wrote 7 paragraphs about how to build something for python when for other languages it’s literally a single command. For Ruby, it’s literally bundle. Nothing else. Doesn’t matter if it’s got C packages or not. Doesn’t matter if it’s windows or not. Doesn’t matter if you have a different project one folder over that uses an older gem or not. Doesn’t matter if it’s 15 years old or not. One command.

Just for comparison for gradle it’s ./gradlew build For maven is mvn install For Elixir it’s mix deps.get mix compile For node it’s npm install

every other language it’s hardly more than 1 command.

Python is the only language that thinks that it’s even slightly acceptable to have virtual environments when it was universally decided upon decades ago to be a tremendously bad idea. Just like node_modules which also was known to be a bad idea before npm decided to try it out again, only for it to be proven to be a bad idea right off the bat. And all the other python build tools have agreed that virtual envs are bad.

and yet that all works fine in Ruby, which came out around the same time as Python and yet has had Bundler for 15 years now.

Python - 15+ package managers and build tools Ruby - 1

the closest language to look at for packaging is probably lua, which has similar issues. however since lua is usually not a standalone application platform it’s not a big deal there.

no the closest language is literally Ruby, it’s almost the exact same language, except the tooling isn’t insane and it came out only a few years after python.

You have been in lala land for too long. That list of things to do is insane. Venv is possibly one of the worst solutions around, but many Python devs are incapable of seeing how bad it is. Just for comparison, so you can understand, in Ruby literally everything you did is covered by one command bundle. On every system.

There’s a good document from the SWAG reverse proxy that explains it all. I reverse proxy everything on my unraid server through swag and have for years.

The longest load for a page you haven’t encountered before is under a second, because it’s loading thousands of items. The longest paint is 176ms. It was averaging like 17ms. It’s incredibly fast.

I definitely can’t show this to my wife

Just as many issues as not reading the article.

The article says this isn’t to affect existing code.

They mean put some space between you.

That means it’s not easy to delete. So your initial premise is wrong.

LinusTechTips has an incredibly recent video on this exact topic. Of course they were immediately sued or whatever so you can only watch on reuploads. https://youtu.be/IsUen26Cufs?si=b94x1EsxjLRi0Bts

I wouldn’t support the company, but I also think certifications are mostly useless.

Man we need a giant comparison table. I looked into these but have been trying out SiYuan.

What problem does this solve that test containers does not? Besides socket access?

Mlem is a lot better than Voyager. Better features, faster, has fewer errors messages. At least for me.

Doesn’t really matter here. The saying is “the man, the myth, the legend”. If you go changing every part of it you might as well have not said anything at all because it won’t make any sense.

My guess is focal length. Most facial photos with tons of detail will be close up selfies with a short focal length, thus increasing size of the face proportionally.

Well are you going to tell us?

I care. Some people care more than others. That’s fine.