News for hackers. Stuff that matters.
Re:Please do not use Python for tooling by falcolas on Tuesday August 16, 2022 @11:01AM (#32483687)
Containers work particularly well for python environments.

You can get them working locally, but it's easiest when the developers stick with the standard library. Needless to say, virtually nobody does.

Re:Please do not use Python for tooling by PurpleRamen on Tuesday August 16, 2022 @11:09AM (#32483815)
But are containers portable? Can you take them, send them per mail or put on a USB-stick? And I'm not talking about the recipe for creating them, but the actual container itself.
Re:Please do not use Python for tooling by falcolas on Tuesday August 16, 2022 @11:13AM (#32483866)
Yes.

The actual image is a tar file, and container runtimes include commands for both exporting and importing. Exceptionally portable. More portable than JAR files and Go binaries, at least.

Re:Please do not use Python for tooling by PurpleRamen on Tuesday August 16, 2022 @11:35AM (#32484201)
Wait, which container are we talking about? Docker? AppImage? Kubernetes? What about the runtime?
Re:Please do not use Python for tooling by jrockway on Tuesday August 16, 2022 @01:40PM (#32486153)
OCI Images. You can run them in Docker, Podman, Kubernetes, systemd-nspawn, etc.

Nobody is going to use your tool if they have to fetch it from a container registry and have to run it isolated from their filesystem and network, though. OCI images are fine if you have a pet app and you have to ship it to a production server. Not that convenient for interactive tools, though. Consider:

  $ docker run -v /tmp/foobar:/tmp/foobar debian:stable ls /tmp/foobar
  a.txt
You really just want to type "ls /tmp/foobar".
Re:Please do not use Python for tooling by falcolas on Tuesday August 16, 2022 @02:44PM (#32486997)
That's something that aliases excel at.