Kevin Dangoor wrote: > Hmm... should the real solution here be that the shell and the toolbox > do a bit more initialization of the environment?
I don't know if that is necessary. Both of patches use the current configuration (when provided), so tg-admin shell will work as expected, encrypting according to your preferences. Even if Shell tries to load identity/visit (when configured), that still won't help in situations where you want to use TG_User in a stand-alone script. The best example I can think of is a test where your setup creates a TG_User, and you haven't initialized identity. (Quickstarted project's nosetests are failing right now because of this). You may want to more fully load the environment, but something like this should be done anyways. Of course, that could have been a rhetorical question, in which case yes, we should most definetly do a bit more initialization of the environment. :-) Seriously, I'm probably only seeing the ramifications of this change, so perhaps you are thinking of other areas where more fully loading identity might be of use. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
