Cliff Wells <[EMAIL PROTECTED]> writes: > Let's all remember this the next time mention of private variables is > raised on c.l.py ;-)
To be told that if SO used _dirty or __dirty it wouldn't happen? It looks like a bug to me that internal variables are "leaking" and interfering. Python already has a convention that if it was used it would probably (I haven't looked the source of SO here to see if there's any name mangling) have avoided this kind of problem... -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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 -~----------~----~----~----~------~----~------~--~---
