I've been using python for two decades and ruby exactly one decade ago for a couple years.

Your comment on packaging is interesting.

My perspective is that packaging on ruby was in nearly the same state ten years ago as python is now.

My team switched ruby package managers several times during the ruby work and none of them ever worked reliably and was a regular root cause of fragility in our builds.

I hope that ruby packaging has settled in that time while python has the same kind of cultural noise that afflicted ruby during that period. Popularity has downsides. Political packaging wars is one of them.

I'm old school enough that I stick with tried and true pip, venv, and .env and its ilk.

There was a long battle in downstream packaging for a while that I just didn't want to be involved in having seen the same thing in ruby.

FWIW, if I were you I'd look at crystal, elixir, or nim. I was very productive in ruby but the near constant battle of wrestling with DSL's that are not concomitant with their parent is, IMHO, to be avoided. I've seen more than one team fall prey to that trap. Caveat emptor - pick your DSL's carefully.