> We seem to be turning into comp.lang.python here. :-(
Good point, I'll try my chance over there. > Sounds like you want to use an exception and have caller catch an > exception of a particular type and then return the value in the > exception object. In fact, I don't want 'called' to throw an exception and 'caller' to catch it (as suggested by Malcolm), nor do I want 'caller' to test the result of 'called' (as suggested by Evert). I would like things to remain completely transparent for 'caller', so the power remains in the hands of 'called'. I'll ask on the Python group and will post an answer here if I get something interesting, just for the sake of closing this post. Thanks! Julien --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
