John Anderson wrote: > These exceptions don't make sense for our customers. The release version > is for them, which is why we don't show them.
But my point is that we as developers will not catch them all. Our users *will* do something weird which will cause exceptions. If they are silently eaten, we may never hear about them. That is why I said I'd ideally like something like the following dialog pop up: Internal Program Error! It is recommended that you restart Chandler to prevent data corruption. [View report before sending] [Send bug report] [Do not send] The report would be simply an email which would contain Chandler version, backtrace, and any other information we might think would help. > The exceptions do make sense for developers, so that's why we have a > version for developers, which is the debug version. If you're concerned > about the performance of the debug version use the release binaries and > turn on __debug__ by removing -O and it will perform pretty well. So if > you're developing, you shouldn't be using -O. Ok, so I will see the dialogs even if I have optimized binaries but take out -O from RunPython? -- Heikki Toivonen
signature.asc
Description: OpenPGP digital signature
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
