On Nov 7, 2007 11:46 PM, Alberto Valverde <[EMAIL PROTECTED]> wrote:
[...] > I think that what Chris has proposed (put __all__ and a comment > explaining why) is a great idea. not necessarily a bad one :) I see the point. I myself use this form and enjoy the benefits so I won't tell it's bad to us it :) [...] > > The usage of __all__ in a nearly empty model.py could lead to strange > > questions in the ML when people try to import something and forgot to > > declare it in __all__. We would have too much questions around this > > and I feel it would be an irritation/frustration to beginners more > > than a help for them. > > A well-worded comment can help mitigate this. And some clear docs then. Because even with good comments just above it, the usage of __all__ and its *real* meaning and impact could be deceptive to someone not used with the intricacies of python. Florent. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
