I'm not sure that's true. It doesn't seem to me that all of the users who encounter the mpmath issue described in the article are inexperienced users. They just aren't experts on the internals of Python, nor should they need to be.
> The real reason for a problem is the existence of multiple syntactical forms for import.
I don't see how removing the "unnecessary" forms (I don't agree that they're unnecessary, but I'm putting that aside here for the sake of argument) would help. Can you elaborate?
> giving up on making them real objects
PEP 562 already moved in the opposite direction, towards making them real objects (or more precisely, towards exposing more of their real object interface at the Python level).
> "unnecessary" forms
The from x import is unnecessary and so is import as. Both can be written like so:
import x.y
y = x.y # from
import x
y = x # as
So, they aren't necessary. You can write any program that uses them without them.> PEP 562 already moved in the opposite direction, towards making them real objects
Who cares? We had dozens of nonsense PEPs, and will have hundreds more. Python isn't known for good planning nor for execution. I'm talking about what should've been done. The nonsense Python does is way over there when it comes to what it should be doing.
I'm more worried that this PEP will make things more confusing for beginners. I see this PEP as a removal of some training wheels. It opens the door for much weirder behavior than warnings/error messages. Whenever I've reached for this feature, it's been to do something "clever" that I probably shouldn't have been doing in the first place. Sure, some people will do wonderful/helpful things with this feature. But lunatics like me will use this to do some absolutely unhinged things.
I hope this PEP gets accepted, but I understand if the maintainers decide it's a bridge too far.
What this PEP suggests is yet another clutch for advanced users. It will allow advanced users to screw with module properties in all sorts of unpredictable ways. Beginners will be just a little bit more screwed if this feature is added. But they are already in such a deep hole if they started with Python... I don't know how to help them except by suggesting they use a different language.
To be fair, mostly nothing in python is a "real problem", it's all just syntactic sugar to make coding more comfortable.
> 3. Modules historically struggled to be "real" objects in Python. So, another direction this could've taken is giving up on making them real objects.
No, go the opposite. Just make them first class objects. There is valuable comfort in this. Python is multi-paradigm anyway.
But... yes, Python has real problems. For example, it has idiotic type system where any sort of logic goes to rest. It's not syntactic sugar. It's just bad (or, if we are honest, absent) planning. It has awful syntax, very difficult to parse. All concurrency primitives it has are worthless trash... just to name a few.
Whatever this PEP is trying to address isn't a real problem by any stretch of imagination, not compared to the host of huge problems Python has. But, really, it's not a problem at all. It's the RTFM kind of "problem".
1. This is not a real problem (this only affects completely inexperienced users for whom everything is a problem anyways).
2. The real reason for a problem is the existence of multiple syntactical forms for import. To solve the problem one would have to remove the unnecessary import forms (but, come on, there isn't really a problem, so nothing needs to be done).
3. Modules historically struggled to be "real" objects in Python. So, another direction this could've taken is giving up on making them real objects. Just make them a syntactic convention (like packages in Java). But, again, there's no real problem here, so nothing needs to be done.