>From what I can tell, there is a port conflict between aptana (or one of its plugins) and web2py. Still drilling down to find the culprit.
If I open aptana first, and let it load up properly, i can not launch web2py. but, I can launch web2py, then aptana without issue. Seems something in aptana (or a plugin I have installed) will not share. ALthough, even if i launch aptana first, then web2py, nothing tells me that there is a weak reference issue. so this is a little strange. GLobals and its use of dict.... that's where I am headed next. Would that make any sense? Thanks, Mart :) On Apr 15, 3:41 pm, mart <[email protected]> wrote: > found the problem.... sorry for the ruckus! > > the problem is aptana. Doing this outside of aptana works fine... not > sure why yet. > > so, the problem is narrowed down. Once I figure out why aptana is mis- > behaving, I'll post results.... > > Thanks for you help!! > Mart :() > > On Apr 15, 3:29 pm, pbreit <[email protected]> wrote: > > > > > > > > > It looks to me like it might be stuck at the very beginning with "import > > os". In MacOS terminal, can you do a simple "import os" in Python shell? > > > $ python > > > >>> import os
