On 8 Nov 2019, at 07:52, Steve Barnes
wrote: Hi,
I hope that his hasn’t been discussed to death in the past but I quite often encounter cases where developers have unwittingly created a file or directory that has a name clash with either a system import or a pip installed library import. This can be very confusing to new users! And, of course, as the number of core libraries and the installable ecosystem grow this potential problem is growing all of the time.
I have been bitten by this too. It seems to me like the import system could raise an error in these cases. This seems like it should solve these problems and avoid the need for new syntax. I guess there's a performance problem with this though, since the import system then can't early return?