Not sure I understand.
Is your problem that you do

python nweb2py.py -a 'password'

and you get?

TypeError: cannot create weak reference to 'classobj' object

I have never seen this before. How do you run it? Which python
version? Do you have a loger traceback?

On Apr 14, 10:47 pm, mart <msenecal...@gmail.com> wrote:
> Hi,
>
> thought it would simple enough to do, but ... surprise , surprise on
> me!
>
> here's the gist: i have some scripts, that do a good part of my day to
> day. functions, modules, etc... are called through a set of navigable
> menus (everything is interactive @ the cmd line) . they look like
> below. What I am trying to do is get option 11 (below) to work...
> option 11 is supposed to bring me to a "web2py" menu where I can
> configure its settings (like, password, Cron (True or False), which
> app to open once the server is running, etc....) works like an ascii
> looking wizard, which works great! but... but I can not get web2py to
> launch. I tried pretty much everything I can think of like 'python
> web2py.py -i 127.0.0.1 -p 8000 -a blabla --nogui', importing widget,
> etc... and using many different options to launch (subprocess,
> os.system, exec, popen, etc...). Ideally, web2py would start without
> invoking the UI.
>
> Now that I have DAL stand-alone and web2py sharing and playing with
> the same tables, I wanted to start making things interesting...
>
> the jam is the weak reference exception popping up...
>
>                 TypeError: cannot create weak reference to 'classobj'
> object
>
> Anybody have a trick handy??? :)
>
> thanks in advance,
> Mart :)
>
> No. | option
> ----------------------------------------------------
> 1.   | kick off a full build
> 2.   | kick off a partial build (specify CMD)
> 3.   | create new build_spec
> 4.   | interactive shell
> 5.   | interface to P4
> 6.   | blueFTP client
> 7.   | dump tables to...(xml or csv)
> 8.   | setup local_user
> 9.   | view local_user table
> 10. | view storage info
> 11. | launch web2py
>
> 12. | back to MAIN MENU
> 13. | quit

Reply via email to