On Thu, Mar 9, 2023 at 9:51 PM Thomas Passin <[email protected]> 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 the function is ready to test. Hmm. The standard way is to raise NotImplemented. Your post reminds me that Leo's do-nothing gui methods call self.oops(). I'm not sure why I used this pattern: raising NotImplemented gives a full traceback, which would seem to be enough. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS3XC3NFjgNFOXYzwo82F8Y%3DMBFEZwftLqfnvrfhccsBaw%40mail.gmail.com.
