[Pydev-users] [pydev - Users] RE: code checking not working for new modules

[SourceForge.net <no...@so...>]

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=3781721
By: xyld

You are right, of course, Fabio.

I _hadn't_ configured my pythonpath correctly, though I thought I had.

Just a suggestion -- perhaps some kind of warning could be generated somewhere
when it _isn't_ using code analysis on a python file, with possible fixes? It's
just that it is a case where it's not immediately obvious that it _isn't_ going,
because you might assume there is nothing wrong with the code :) In fact when
it did switch on, the only problems I had were import errors.

One more question, somewhat related: some of the .so files aren't being picked
up from my python path, in this case the lxml etree.so (installed
in site-packages/lxml-1.0.1-py2.4-linux-i686.egg/lxml/etree.so). Is there any
way to force that?

Many thanks,

Richard.

______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: 
https://sourceforge.net/forum/unmonitor.php?forum_id=293649