It is not better. The web2py shell is the normal Python shell or the
IPython shell if available. The difference is that the code in the web2py
shell has already imported for you web2py environment (and optionally the
models) so it it like coding in a web2py controller:
>>> python
>>> print db.t
By "built-in" shell, do you mean the one in the admin app? I think there
are sometimes problems with that (particularly with database operations),
so I tend to use the web2py shell in the terminal, which you can start as
follows from the web2py directory:
python web2py.py -S yourapp/[optional c
yes. so when working with DAL directly from the shell it's better to
work from the web2py shell in the terminal rather than the admin app
shell? any idea why?
On Fri, Apr 5, 2013 at 2:43 PM, Anthony wrote:
>
> By "built-in" shell, do you mean the one in the admin app? I think there are
> sometim
Well, give the admin shell a try and see if it works. I just had some
problems in the past with db operations not committing (at least on
Windows) -- not sure why. I think the terminal shell is easier to use
anyway (don't have to type "print" before every command, recall previous
command, etc.)
The admin shell has problems maintaining state. I do not consider it
reliable. The terminal shell is rock solid. It is a normal pyhton shell.
On Friday, 5 April 2013 16:48:50 UTC-5, Michael Herman wrote:
>
> yes. so when working with DAL directly from the shell it's better to
> work from the web
Yes, Massimo already explained this in the past, and I've added this note
on http://web2py.com/books/default/chapter/29/03#Design (under the Shell
paragraph):
Be careful using the web based shell - because different shell requests
will be executed in different threads. This easily gives errors, es
Today I discovered an other problem with the admin shell.
If I execute command 1
and then command 2, at this point it will re-execute command 1 too.
If then I execute command 3, it will execute again also 1 and 2.
This is while running web2py from source code on Windows with simple
python web2py.
Please open a ticket about this. This is a major issue. Perhaps we should
remove the web based shell.
On Wednesday, 13 August 2014 02:41:17 UTC-5, Giacomo Dorigo wrote:
>
> Today I discovered an other problem with the admin shell.
> If I execute command 1
> and then command 2, at this point it wi
OK, how do I open a ticket?
On Wed, Aug 13, 2014 at 8:04 PM, Massimo Di Pierro <
massimo.dipie...@gmail.com> wrote:
> Please open a ticket about this. This is a major issue. Perhaps we should
> remove the web based shell.
>
>
> On Wednesday, 13 August 2014 02:41:17 UTC-5, Giacomo Dorigo wrote:
>
https://code.google.com/p/web2py/issues/entry
On Saturday, 16 August 2014 23:08:36 UTC-5, Giacomo Dorigo wrote:
>
> OK, how do I open a ticket?
>
>
> On Wed, Aug 13, 2014 at 8:04 PM, Massimo Di Pierro <
> massimo.dipie...@gmail.com> wrote:
>
>> Please open a ticket about this. This is a major issu
I don't know,
for some reason it does not leave me submit the ticket:
Windows 8
web2py :
2.9.5-stable+timestamp.2014.03.16.02.35.39
(Running on Rocket 1.2.6, Python 2.7.7)
What steps will reproduce the problem?
1. run web2py from source code from a .bat file python
path_to_web2py/web2py.py
2. at
After truncate the table did you db.commit()?
On Sunday, 17 August 2014 23:17:29 UTC-5, Giacomo Dorigo wrote:
>
> I don't know,
> for some reason it does not leave me submit the ticket:
>
> Windows 8
> web2py :
> 2.9.5-stable+timestamp.2014.03.16.02.35.39
> (Running on Rocket 1.2.6, Python 2.7.7)
no I didn't.
Anyway, now I just tried without opening the two prompt, just opening the
GUI from the .bat file, and I didn't truncate the table, I just did an
insert. Then I tried to input some other commands and it keeps repeating
the insert. So it seems it's not the truncate.
I tried also the db.c
13 matches
Mail list logo
