That is a python design principle https://en.wikipedia.org/wiki/Zen_of_Python
Now there are multiple (sometimes very confusing) ways to import stuff in python, so I am not quite sure if this principle is being followed.
There are many different ways to package Python, none of them are feature complete, and the result is an absolute maintenance nightmare for those of us who have to maintain tools that have Python dependencies.
Perl got packaging right, there's one way to do it, and it just works!
This is a huge barrier to entry for the first time or casual contributor. And when you try to figure it out (or figure it out again), you have to triage all the old and new overlapping documentation.
In practice, perl came closer to achieving this than python.
I've been coding in Perl for 20 years, I'm a CPAN author [1] and I just published my third CPAN contribution yesterday.
I've written over half a million Perl lines of currently in use enterprise cloud software[2] and I'll keep coding in Perl because I don't like the big snake dictatorship of "There should be one — and preferably only one — obvious way to do it."
[1] https://metacpan.org/author/ERUCI
[2] https://aws.amazon.com/marketplace/seller-profile?id=434e986...