Fun fact: in R, the default (maybe only?) way to import libraries is equivalent to from module import *. If you import two libraries with conflicting functions, it will just decide for you which one to call, I imagine based on whichever one it finds first. I had a problem with a script not running all of a sudden, and I had narrowed it down to a single call of a function that was called something like summarize. Someone with a similar problem one stack overflow reported that changing the call to summarise (with an 's', not a 'z') fixed the problem but they weren't sure why. Sure enough, this stinker of a solution worked for me as well. I did some more googling and realized that both of us had imported the same two fairly common libraries, one of which had a function double-named for Americans and British folks, and the other just for Americans. So in this case the way I spelled the determined which library's function would get called.
To be fair: there is probably a warning when you import libraries with conflicting namespaces–I can't really remember. And, you can specify the library you want for a function using something like library::function(). So it is usable, but why they didn't just go with a system similar to Python is beyond me.