Thread: [Pydev-users] [Users] java.lang.RuntimeException: PyLint ERROR:
Brought to you by:
fabioz
From: SourceForge.net <no...@so...> - 2011-12-10 19:18:29
|
The following forum message was posted by piotr_dobrogost at http://sourceforge.net/projects/pydev/forums/forum/293649/topic/4874783: In the error log there are errors originating from plug-in [code]org.python.pydev.core[/code] like this one [code]java.lang.RuntimeException: PyLint ERROR: Traceback (most recent call last): File "C:\python\virtualenv\x\Lib\site-packages\pylint\lint.py", line 31, in <module> from pylint.checkers import utils ImportError: No module named pylint.checkers at org.python.pydev.builder.pylint.PyLintVisitor$PyLintThread.passPyLint(PyLint Visitor.java:238) at org.python.pydev.builder.pylint.PyLintVisitor$PyLintThread.run(PyLintVisitor .java:107) [/code] |
From: SourceForge.net <no...@so...> - 2011-12-13 18:00:00
|
The following forum message was posted by fabioz at http://sourceforge.net/projects/pydev/forums/forum/293649/topic/4874783: It seems you specified the PyLint location but it's not available in the PYTHONPATH for the interpreter you're using... |
From: SourceForge.net <no...@so...> - 2011-12-19 21:34:35
|
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. |
From: SourceForge.net <no...@so...> - 2012-01-12 17:50:42
|
The following forum message was posted by piotr_dobrogost at http://sourceforge.net/projects/pydev/forums/forum/293649/topic/4874783: Any comments on this? |
From: SourceForge.net <no...@so...> - 2012-01-20 14:36:58
|
The following forum message was posted by piotr_dobrogost at http://sourceforge.net/projects/pydev/forums/forum/293649/topic/4874783: [quote]I think that changing the way PyDev runs pylint (specifying interpreter's name before path to pylint script) would solve this problem.[/quote] Fabio, what do you think? |
From: SourceForge.net <no...@so...> - 2012-01-25 18:54:18
|
The following forum message was posted by fabioz at http://sourceforge.net/projects/pydev/forums/forum/293649/topic/4874783: Yes, I think that there are improvements needed to make PyLint have a better integration in PyDev... (I must say I'm not giving a high priority for that because with the pep8 integration and the code-analysis built into PyDev, which are already better integrated, PyLint is becoming less useful, so, I wanted to know which features do you use of PyLint -- to know if it's worth spending more time to improve its integration). Cheers, Fabio |
From: SourceForge.net <no...@so...> - 2012-01-25 21:28:51
|
The following forum message was posted by piotr_dobrogost at http://sourceforge.net/projects/pydev/forums/forum/293649/topic/4874783: Thanks for answering. From time to time I go through all Pylint's warnings and check code to see what I can do to remove them. It's good there's PEP8 integration now. To tell the truth I thought it would overall be better to make Pylint check all things PEP8 checks; see my question at http://stackoverflow.com/questions/6879640/ It looks like nothing happens with http://www.logilab.org/ticket/82519 I'd like to make a remark this problem is probably not specific to Pylint. If there were other 3rd party libs called by PyDev the problem would be the same. Maybe there are already such libs which I'm not aware of... |
From: Nikolaus R. <Nik...@ra...> - 2012-01-26 16:08:39
|
SourceForge.net <no...@so...> writes: > The following forum message was posted by fabioz at http://sourceforge.net/projects/pydev/forums/forum/293649/topic/4874783: > > Yes, I think that there are improvements needed to make PyLint have a better > integration in PyDev... (I must say I'm not giving a high priority for that > because with the pep8 integration and the code-analysis built into PyDev, which > are already better integrated, PyLint is becoming less useful, so, I wanted > to know which features do you use of PyLint -- to know if it's worth spending > more time to improve its integration). My main reason for using PyLint is its more powerful type inference. PyLint is able to warn me about accessing non-existent attributes or calling functions with the wrong signature in many more cases than PyDev is. Best, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C |