Ed Leafe wrote: > On Sep 27, 2009, at 3:40 PM, Paul McNett wrote: > >> This has been on my list for a while. I regret doing it this way: >> should have just >> left these in dabo.settings. I'd like to change it but don't see how >> at this point. > > > Agreed. I found several places where dabo.settings was used, but it > would be really difficult to track down all the dabo.* versions. I > figured that I would at least put a note in there so that anyone who > looks at that import statement doesn't think we're total n00bs.
For the lurkers, we have a namespace, dabo.settings, where global settings are stored. That isn't the problem, and is fine and dandy. The problem is that we, inside dabo.__init__, say "from dabo.settings import *". So now we effectively have copied the dabo.settings namespace into the dabo namespace. I did this, I remember doing it, and I remember thinking I was being smart or clever by doing it this way. I'd save countless developers the time of having to type 'dabo.settings.' instead of 'dabo.' I pretty quickly realized my error: now we have two namespaces that are copies of each other, and no way of knowing if appdev code is modifying dabo.<setting> or dabo.settings.<setting> And there isn't a really great way to deprecate this behavior, either. Hence, the behavior stays. Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[email protected]
