Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

abstract instead of NotImplementedError #27

Open
GoogleCodeExporter opened this issue Mar 16, 2015 · 0 comments
Open

abstract instead of NotImplementedError #27

GoogleCodeExporter opened this issue Mar 16, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

Many methods use "abstract" instead of raising NotImplementError when they are 
destined to be implemented by a child class.

Fun fact, upon research.  I end up in 
http://norvig.com/python-iaq.html
finding an explanation for this.

Still, I think that, to avoid confusion, it should be fixed to either 
abstract() as in the FAQ or just RaiseNotImplementedError.

Otherwise, it will raise NameError which is confusing (and abstract could 
potentially be defined globally)

Original issue reported on code.google.com by alexhans...@gmail.com on 11 Oct 2011 at 6:13

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant