3 ms·
> this only affects completely inexperienced users I'm not sure that's true. It doesn't seem to me that all of the users who encounter the mpmath issue describ
by pdonis 3y ago
> this only affects completely inexperienced users
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).
- crabbone 3y agoYou need to be at the level where you understand the difference between import x and from x import. This comes after couple months of training. And if after that you accidentally mistype it -- well, you'll know where to look for a potential error. It is not a problem for anyone with significant Python experience. > "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.