[wingide-users] pylint environment

Aleh Arol aleh.arol at gmail.com
Mon Aug 27 13:10:11 MDT 2012

Got it. Thanks. Yes, I have custom interpreter set in the project and as we already discussed it seems that doesn't matter because #!/use/bin/python explicitly selected in pylint. 
For true integration pylint panel should do something like $(project_python) pylint.py instead of calling the bin cmd set when configuring pylint panel...
Pylint executable is indeed 4 lines script importing pylint module and running it's instance.
As for the core I 'm pretty sure both pythons I have are 2.7, something went wrong during module import, and if this will keep happening with my custom python (pydebug enabled one) - I'll investigate.

Best regards,
Aleh Arol

Aug 27, 2012, в 18:30, Wingware Support <support at wingware.com> написал(а):

> Wingware Support wrote:
>> It may be, however, that using that entire path will crash pylint b/c it's compiled for another version of Python.  Extension modules are compiled specific to a major release of Python (like 2.6 vs. 2.7 vs. 3.2, etc).  If that's the case you're stuck with manually adding path items in Python Path in Project Properties.
> Sorry, I just need to correct a misstatement I made in the above:  PyLint isn't compiled for that version of Python...  The issue is that the #!/usr/bin/python may be selecting a Python version that isn't compatible with your Python Path.  This should only be a problem if it's a finding an extension module that pylint happens to import as part of its normal operations, such as something in the standard library.  As I think I noted before PyLint doesn't actually execute any code so it won't be importing your modules for real.
> Please let me know if this still isn't clear.
> Thanks,
> -- 
> Stephan Deibel
> Wingware | Python IDE
> Advancing Software Development
> www.wingware.com

More information about the wingide-users mailing list