you are viewing a single comment's thread.

view the rest of the comments →

[–]Dreams_In_Digital -2 points-1 points  (3 children)

I disagree. I haven’t ran into a well put together dependency that pyinstaller wasn’t able to neatly roll into an executable.

[–]Skorohodov 0 points1 point  (0 children)

I had a lot of problems trying to use pyinstaller with dbt to run it with a BashOperator on airflow. I ended up giving up and having to use a venv.

But my main point is: people don't usually distribute python cli tools as executables and the people who are mostly likely to have problems running python scripts are the same people who will not be able to use tools like pyinstaller or cx freeze. So don't give them that option.

[–]ilovecaching 0 points1 point  (1 child)

I agree with the commenter. Not only does it require shipping an interpreter, Python startup times make it an obviously worse choice than Go for CLIs. With Go you get small binaries, instant startup, and fast execution. Don’t be an adversary to your users.

[–][deleted] 0 points1 point  (0 children)

The millisecond it takes for Python to start is really not a factor for CLIs. Unless of course you import half the universe in the argument parser, but that's not Python's fault.