I'm not sure I understand your distinction regarding web2py "running in the background". I think the web shell is intended to emulate the functionality of the standard Python shell as much as possible. In both cases, you're in a REPL where your statements are evaluated in the same environment in which a web2py controller action would be evaluated (i.e., the environment includes all the web2py globals, as well as anything defined in your models as well as the controller if you have chosen to run it). Are you observing something you can do in the web shell that isn't working in the regular Python shell? What exactly are you trying to do? Anthony
On Monday, July 11, 2011 3:39:13 AM UTC-4, Valter Foresto wrote: > Thanks Anthony, > I believe that : > > - when we use *web2py Web Shell* we have all the web2py system running > in the background concurrently > - when we use a *Python console with web2py* (like standard or IPython > for example) we have (like web2py Web Shell) the complete web2py > environment > available but not running in the background. In this case we need to have > more understanding about web2py internal functionality to be effective. I > very appreciate If you can suggest some examples / resources about this > mode > of interaction with web2py environment. I have already tryed, reading from > the web2py book, you suggestion before, furthermore an example of use can > be > very helpfull for all people that want to use web2py deeply. > > - Valter >
