Friend, while I appreciate the time and effort on the docs, it has a rather tiny section on one of the truly worst aspects of pip (and the only one that really guts usability): package conflicts.
Due to the nature of Python as an interpreted language, there is little that you can check in advance via automation around "can package A and package B coexist peacefully with the lowest common denominator of package X"? Will it work? Will it fail? Run your tool/code and hope for the best!
Pip is a nightmare with larger, spawling package solutions (i.e. a lot of the ML work out there). But even with the freshest of venv creations, things still go remarkably wrong rather quick in my experience. My favorite is when someone, somewhere in the dependency tree forgets to lock their version, which ends up blossoming into a ticking time bomb before it abruptly stops working.
Hopefully, your experiences have been far more pleasant than mine.
Unspoken here is the third option: navigate a series of untextured raised rectangular platforms littered with smaller rectangles that will fire you automatically if you touch them, designed by an 8 year old that got bored halfway through the engineering phase and wandered off to play Breakin Story 2.
The good news is that, for only 399 robux a month, you can get VIP membership, which includes a coil that allows you to immediately jump over the entire platform and land into a dated pile of two dimensional meme sprites they meant to clean up.