Thanks. I updated and using this code disappeared with the errors on 'FORM' and 'INPUT'. 'db', 'request', 'session', 'response' still with error.
On Mar 3, 8:20 pm, Anthony <[email protected]> wrote: > Which version of web2py are you using? If the latest (1.99.6), you should > be able to do: > > if 0: > from gluon import * > > That imports the entire API, including dummy request, response, session, > cache, and T objects. Does that remove the errors? > > Anthony > > > > > > > > On Saturday, March 3, 2012 4:42:43 PM UTC-5, Marcelo Zamperetti wrote: > > > I'm trying to use Eclipse + Pydev to develop a web2py application. > > On my controller, Eclipse highlights as errors all the stuff that I'm > > using from web2py, like 'request', 'session', 'db', 'FORM', 'INPUT' > > and so on. > > I did a good deal of searching, but didn't find any real solution. > > What seems to be the most common solution is doing like > > if 0: > > session = None > > [...] > > > I tried importing those 'missing' classes explicitly, but wasn't able > > to do that for all the errors, and if I remember right, the imports > > themselves were marked as errors (like I will describe below). > > > Another similar problem: when I import my own modules, which are on > > the 'modules' directory, it also highlights the import as an error: > > 'Unresolved import: xxx', it works, I can call the functions from my > > module, but it is highlighted as an error. > > > I liked web2py most of all frameworks, but I simply can't work with > > all those 'errors'. First because they are *very* annoying, and > > because there are so many of them, I will often overlook an error that > > is really an error, and also spend more time looking for it, and that > > is counter-productive. > > > Thanks a lot for any information.
