The following forum message was posted by piotr_dobrogost at http://sourceforge.net/projects/pydev/forums/forum/293649/topic/4874783:
Yes and no :) Running [code]c:\python\virtualenv\x\Lib\site-packages\pylint\lint.py[/code] from within command line with the same virtualenv activated results in the same error, indeed. However running [code]python c:\python\virtualenv\x\Lib\site-packages\pylint\lint.py[/code] gives no errors. That's because virtualenv's python executable is on the [code]PATH[/code] but [code].py[/code] extension is still associated with the original Python installation. See http://stackoverflow.com/questions/4879624/ I think that changing the way PyDev runs pylint (specifying interpreter's name before path to pylint script) would solve this problem. ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ Pydev-users mailing list Pydev-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pydev-users
