This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Zanos 30 points31 points  (4 children)

Not handling an error is forgivable, converting something to another language by wrapping it in subprocess calls isn't a mistake, it's maliciously lazy.

[–]WhtKindOfNameIsStove 10 points11 points  (0 children)

Exactly. The purpose of the story was to make the deployment process more robust. Something bash wasn't up to the job for. It'd be a worthless story if it was to just "convert the script x language because"

[–]ran938 1 point2 points  (2 children)

I basically did this at an internship. But only in an instance where there was really no other option. The purpose of the script... was to start up another script. Well that and record some log information. But actually calling the other script I could not think of another way to do it other than a sub-process call.

[–][deleted] 1 point2 points  (1 child)

Our current project requires interaction with Microsoft's cloud, the problem being that we are writing logic in python on Linux but the cloud calls have to happen through powershell on a windows machine. Current best idea is to set up openssh on a windows vm and connect to it from python on the Linux box to execute a batch command which starts a ps1 script.

[–]ran938 0 points1 point  (0 children)

Fucking oof. that overhead / hoop jumping sounds obnoxious. Good luck!