Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
This is in the docs. To paraphrase: Used for abstract methods that must be overridden in subclasses When the implementation is still WIP, but you want to leave a placeholder for the method name...
Answer
#2: Post edited
by
matthewsnyder
·
2024-07-08T19:50:46Z (6 months ago)
This is in the [docs](https://docs.python.org/3/library/exceptions.html#NotImplementedError).* abstract methods should raise this exception when they require derived classes to override the method* while the class is being developed to indicate that the real implementation still needs to be addedIt's a way to have a placeholder method name to "reserve namespace", but with the actual method body "coming soon".
- This is in the [docs](https://docs.python.org/3/library/exceptions.html#NotImplementedError). To paraphrase:
- * Used for abstract methods that must be overridden in subclasses
- * When the implementation is still WIP, but you want to leave a placeholder for the method name and signature
- It's a way to to "reserve namespace", but with the actual method body "coming soon" (from you or someone else).
#1: Initial revision
by
matthewsnyder
·
2024-07-07T19:13:57Z (6 months ago)
This is in the [docs](https://docs.python.org/3/library/exceptions.html#NotImplementedError). * abstract methods should raise this exception when they require derived classes to override the method * while the class is being developed to indicate that the real implementation still needs to be added It's a way to have a placeholder method name to "reserve namespace", but with the actual method body "coming soon".