[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=3784718
By: xyld

Hi Fabio:

Regarding fixes: the fixes were something I wasn't really counting on. I guess
a "really nice to have" though would be something that tells you that code-analysis
isn't switched on for a particular python file. It's not immediately obvious
why things like "unused variable" don't work on a random python file :)

Regarding folders in python path: I should explain that the module in question
(lxml) has been installed from a python 'egg', as seems to be becoming more
popular. The egg directories are in the python path, but they _don't_ have an
__init__.py in them, because they're not the actual module directories, but
rather just _contain_ the module directories. The 'egg' installer (easy-install)
puts an easy-install.pth in the site-packages directory, which then adjusts
the python path. The only interim solution I can think of is to setup, individually,
all the 'eggs' I've installed.


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