I am not sure this is necessary: RuntimeError already encapsulates this
somewhat well. You'll find RuntimeError already widely used, especially in
concurrency where it is easy to get into a situation where the state is invalid
for a specific action.
I stumbled upon PEP 671 again today, and for what it's worth I fully agree with
everything said here.
For the same reasons as you listed, I am generally opposed to PEP 671. Wrapping
functions in one way or another is extremely common and this PEP will make a
problem which is currently super
I am not fully aware of how ssl.SSLContext is used, but adding __slots__ would
prevent this. You would see an error similar to: AttributeError: 'MyClass'
object has no attribute 'my_attribute'
___
Python-ideas mailing list -- python-ideas@python.org
To
