Ezio Melotti added the comment:
I think we should be pursued together with #18156, so I'm going to close this.
Serhiy already added a reference to this issue there.
--
nosy: +ezio.melotti
resolution: - duplicate
stage: - resolved
status: open - closed
flying sheep added the comment:
sure, go ahead! i wasn’t aware of PEP nor issue, so sorry for filing a dupe.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22716
___
flying sheep added the comment:
No, this is about the object which misses an argument, not the attribute name.
But thanks for the pointer: one combined fix for both would be the smartest
thing to do.
--
status: closed - open
___
Python tracker
Changes by R. David Murray rdmur...@bitdance.com:
--
resolution: duplicate -
stage: resolved -
superseder: Add an 'attr' attribute to AttributeError -
versions: +Python 3.5 -Python 3.6
___
Python tracker rep...@bugs.python.org
Serhiy Storchaka added the comment:
See also PEP 473.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22716
___
___
Python-bugs-list mailing list
New submission from flying sheep:
Trying to replicate a Ruby Gem that raises a “did you mean” error when
mistyping a method name, I hit a showstopper:
There seems to be no way to get the object which misses an attribute from an
AttributeError.
I propose the appended patch (it might be
Serhiy Storchaka added the comment:
This is a duplicate of issue18156.
--
nosy: +serhiy.storchaka
resolution: - duplicate
stage: - resolved
status: open - closed
superseder: - Add an 'attr' attribute to AttributeError
___
Python tracker
