Re: For Devs: An @notImplemented Decorator

" pylint prefers NotImplementedError." - EKR Often during development I prefer not to handle an exception, and want the program continue to run. Though I suppose I could put exception handling into the decorator. -- You received this message because you are subscribed to the Google Groups "

Re: For Devs: An @notImplemented Decorator

On Fri, Mar 10, 2023 at 7:17 AM Edward K. Ream wrote: PR #3200 removes all > gui-related `oops` methods. This method has been moved into devel. I meant: this *branch* has been *merged* into devel. EKR -- You received this message because y

Re: For Devs: An @notImplemented Decorator

On Friday, March 10, 2023 at 5:44:25 AM UTC-6 Edward K. Ream wrote: Hmm. The standard way is to raise[NotImplementedError]. PR #3200 removes all gui-related `oops` methods. This method has been moved into devel. I have tested the new code wi

Re: For Devs: An @notImplemented Decorator

On Friday, March 10, 2023 at 5:44:25 AM UTC-6 Edward K. Ream wrote: Hmm. The standard way is to raise NotImplemented. pylint prefers NotImplementedError. See this question . Edward -- You received this message because you are subscribed to the G

Re: For Devs: An @notImplemented Decorator

On Thu, Mar 9, 2023 at 9:51 PM Thomas Passin wrote: > It can be helpful to be able to handle functions/methods that have not > been implemented. This is often done by having them print a string (such > as "Not Implemented") and returning. This is a bit clumsy and one needs to > edit it out when