There is a special handling of `__hash__` set to None in the interpreter
core. This is because every class inherited the `__hash__` attribute
from "object", and setting `__hash__ = None` is a simple way to make it
unhashable. It makes hash() raising the correct type of exception
(TypeError),
Denis Kotov writes:
> Yes, C++ ABI is specific to each compiler, but it is not a problem,
> because you will anyway recompile CPython for each compiler !!
Right, but the point is that we want few C++ compilers people really
use to get upset by Python code. Since most changes are backward
Stephen J. Turnbull wrote:
> The point of C++ standard support level is linking CPython to external
> codebases using C++, and at least for the standard CPython currently
> supports, the C++ ABI is specific to each compiler and version (for
> some compilers), right?
Yes, C++ ABI is specific to
Denis Kotov writes:
> From huge codebase experience with C++, it does not cause
> significantly better (1) Readabillity or (2) Maintainability on its
> own compared to C
But that's not what we're talking about. "Port CPython to C++" is a
perennial suggestion that gets rejected fairly
On Fri, Apr 29, 2022 at 8:12 PM Python tracker
wrote:
> ACTIVITY SUMMARY (2022-04-22 - 2022-04-29)
> Python tracker at https://bugs.python.org/
>
> To view or respond to any of the issues listed below, click on the issue.
> Do NOT respond to this message.
>
> Issues counts and deltas:
> open
