News for hackers. Stuff that matters.
Re:Pyinfra: Automate Infrastructure Using Python by DandyDev on Tuesday April 30, 2024 @02:43PM (#40214609)
Why is it important to be able to build into portable binaries? Pyinfra doesn't require running Python on the machines you manage. Pyinfra basically turns your Python code into shell commands which it runs over SSH. So only your development machine has to run Python.

I think there is not a lot of overlap between people who need to automate infrastructure and people who don't know how to install Python on their development machine.

As for your other comments regarding Python as a language: I mostly agree. I have stepped away from Python as a language to develop production software. In Python I miss the confidence I get from static typing. Having said that, for automating infrastructure, you're effectively comparing Pyinfra and Python to bash scripts and YAML (for things like Ansible), which are both orders of magnitude worse if you like static typing or any form of being able to verify what you wrote.

Re:Pyinfra: Automate Infrastructure Using Python by yjftsjthsd-h on Tuesday April 30, 2024 @08:37PM (#40218205)
N=1 I'm capable of handling python on my dev/deploy box(es), but that doesn't mean it's not a pain. In my perfect world, ansible/puppet/chef/whatever would ship as a single static binary even when they mostly ran against remote SSH targets.
Re:Pyinfra: Automate Infrastructure Using Python by BirAdam on Tuesday April 30, 2024 @10:50PM (#40218996)
Right, but this makes me wonder why I can’t just do: ssh user@host “echo ‘Hello World’”

All these kinds of tools essentially just executing commands over SSH… I could just SSH.

Re:Pyinfra: Automate Infrastructure Using Python by fire_lake on Wednesday May 01, 2024 @02:49AM (#40220285)
> So only your development machine has to run Python.

If you have a team of developers and a CI process, then portability is important. There isn’t one development machine.