News for hackers. Stuff that matters.
Re:How to improve Python packaging, or why 14 tools are at l... by int_19h on Tuesday January 17, 2023 @07:55PM (#34421888)
Is there any reason why `python foo.py` couldn't do the equivalent of what `cargo run` does, if that's the expectation of most users?
Re:How to improve Python packaging, or why 14 tools are at l... by uranusjr on Tuesday January 17, 2023 @08:28PM (#34422218)
Most of those workflow tools support at least two execution contexts, one for development and one for deployment (`cargo run` vs executing the compiled binary directly, `npm run` vs `node foo.js`, etc.). There are various reasons for the separation including hidden build steps or to set up the runtime environment, generally you want certain things automated during development but not when the program is deployed. A more accurate way to say this `python foo.py` can’t replace `cargo run` while still doing what it currently does; obviously it could be changed to run the program in the development context. The problem is it’s currently used in multiple contexts, and nobody really wants their workflow to break.