Neil Blakey-Milner wrote: > "proper imports" returns the > "session"-and-"Session"-in-the-same-namespace problem, though.
Yes, that may lead to some user confusion. > By the way, the capital "Session" still irks me. Sure, it's a > (constructed) class, but it's being treated as a (non-class) object, > and I don't see how using Session is any semantically different to how > we use a StackedObjectProxy or any other sort of proxy/facade. > Implementation details don't seem as important as how it feels to use > it. +1. > Anyway, we're back to a namespace collision (even if only in people's > heads) if we're expecting people to get used to having "Session" and > "session" both in scope. I agree. Alex --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
