On 2 February 2012 11:18, Ethan Furman <et...@stoneleaf.us> wrote: > Implementation questions for the __NoException__ route: > > 1) Do we want double underscores, or just a single one? > > I'm thinking double to mark it as special as opposed > to private. >
Double and exposed allows someone to explicitly the __cause__ to __NoException__ on an existing exception. > 2) This is a new exception class -- do we want to store the > class itself in __context__, or it's instance? If its > class, should we somehow disallow instantiation of it? > > 3) Should it be an exception, or just inherit from object? > Is it worth worrying about somebody trying to raise it, or > raise from it? > If it's not actually an exception, we get prevention of instantiation for free. My feeling is just make it a singleton object. > 4) Is the name '__NoException__' confusing? Seems perfectly expressive to me so long as it can't itself be raised. Tim Delaney
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
