An unbiased evaluation of Python environment and packaging tools (2023)

Re:An unbiased evaluation of Python environment and packagin... by GorsyGentle on Monday April 15, 2024 @08:37PM (#40047185)

In a way I'm glad it's not mentioned. As a FreeBSD user, nothing is more disheartening than to find a cool and interesting project written in a great^1 language without any packaging or distribution method other than "here's my container bruh". Like, ughh.

^1 Caveat, making a package of a Python project can be a rabbit hole can be a real pita. Virtual envs are usually good enough for most stuff until I start to need a compiler in every jail. Nowadays I'm looking almost only at Go (best) or Rust because their distribution is trivial in comparison.

[ Parent | on HN ]

Re:An unbiased evaluation of Python environment and packagin... by ethagnawl on Tuesday April 16, 2024 @10:18AM (#40052250)

I'm with you on pretty much all of what you've said. The _trivial distribution story_ is part of the reason I handed off maintenance of tmuxinator and started working on rmuxinator (spiritual successor written in Rust).

Otherwise, I often find myself needing to deploy Python/Node/Ruby at $WORK and I'd really rather not try to get a bunch of dev/prod machines (possibly running different OSes!) trying to use whatever the flavor of the day for managing virtual environments, interpreter versions, packages, etc. is.

[ Parent | on HN ]