[issue15767] add ModuleNotFoundError

2018-02-26 Thread Christoph Groth
Christoph Groth <christ...@grothesque.org> added the comment: > Read Eric's message before mine. Of course I read it, I wouldn't have asked otherwise. Eric mentions an older message ("see msg182332") that *predates* your judgment that "outside importlib t

[issue15767] add ModuleNotFoundError

2018-02-26 Thread Christoph Groth
Christoph Groth <christ...@grothesque.org> added the comment: My curiosity was piqued when I saw ModuleNotFoundError, so I decided to look it up. This led me to this page and I read the complete discussion. I still did not understand the decision, so I allowed myself to ask, also bec

[issue15767] add ModuleNotFoundError

2018-02-26 Thread Christoph Groth
Christoph Groth <christ...@grothesque.org> added the comment: In the above, please replace "understand the decision" by "understand the usefulness of it". In the above discussion, as an alternative to a new exception, it was proposed to add an attribu

[issue15767] add ModuleNotFoundError

2018-02-26 Thread Christoph Groth
Christoph Groth <christ...@grothesque.org> added the comment: I'm trying to understand why ModuleNotFoundError was added to 3.6. The "what's new" entry links to this page. Looking at the discussion, Guido said in 2013: "Right. Outside importlib there shouldn't be

[issue15767] add ModuleNotFoundError

2018-02-27 Thread Christoph Groth
Christoph Groth <christ...@grothesque.org> added the comment: Thank you, Chris, for your reply. If this is indeed the main use case of ModuleNotFoundError, I respectfully suggest to document it better. The way things are now, Python users who switch to 3.6 encounter this new exc

[issue15767] add ModuleNotFoundError

2018-02-27 Thread Christoph Groth
Christoph Groth <christ...@grothesque.org> added the comment: Unfortunately I do not feel competent enough to submit a documentation patch because I still do not understand why ModuleNotFoundError was added. I don't want to bother you further with this. Thank you all for your prompt r

[issue43475] Worst-case behaviour of hash collision with float NaN

2021-11-24 Thread Christoph Groth
Christoph Groth added the comment: Hello. I would like to point out a possible problem that this change to CPython has introduced. This change looks innocent, but it breaks the unwritten rule that the hash value of a number (or actually any built-in immutable type!) in Python depends only

[issue43475] Worst-case behaviour of hash collision with float NaN

2021-11-24 Thread Christoph Groth
Christoph Groth added the comment: > What concrete action would you propose that the Python core devs take at this > point? Nothing for now. I stumbled across this issue through https://gitlab.kwant-project.org/kwant/tinyarray/-/issues/20 and had the impression that the aspect