Revision history [back]
Yes, it works in Wing 7 with a bit of extra configuration. The way to enable PyLint for a remote host in the Code Warnings tool is:
1) Go to the Configuration tab in the Code Warnings tool and check on "Enable external checkers" and then click on the Configure button that appears.
2) Under the PyLint tab in the configuration dialog check on Enabled and then you will need to edit the default Command Line to replace ${WING:PYTHON} with the full path to the Python you want to run PyLint under on the remote host.
Submit the dialog and the Code Warnings tool should update to show any warnings from Wing and PyLint together in the Warnings tab, and also inline on the editor.
If this doesn't work, you can see the output of the PyLint call in the console, which you can show from the Options menu in the Command Line tool.
Please let me know you have other questions or can't get it working.
Yes, it works in Wing 7 with a bit of extra configuration. The way to enable PyLint for a remote host in the Code Warnings tool is:
1) Go to the Configuration tab in the Code Warnings tool and check on "Enable external checkers" and then click on the Configure button that appears.
2) Under the PyLint tab in the configuration dialog check on Enabled and then you will need to edit the default Command Line to replace ${WING:PYTHON} with the full path to the Python you want to run PyLint under on the remote host.
Submit the dialog and the Code Warnings tool should update to show any warnings from Wing and PyLint together in the Warnings tab, and also inline on the editor.
If this doesn't work, you can see the output of the PyLint call in the console, which you can show from the Options menu in the Command Line tool.
Please let me know you have other questions or can't get it working.
Yes, it works in Wing 7 with a bit of extra configuration. The way to enable PyLint for a remote host in the Code Warnings tool is:
1) Go to the Configuration tab in the tool and check on "Enable external checkers" and then click press on the Configure button that appears.appears
2) Under the PyLint tab in the configuration dialog that appears check on Enabled and then you will need to edit the default Command Line to replace ${WING:PYTHON} with the full path to the Python you want to run PyLint under on the remote host.
Submit the dialog and the Code Warnings tool should update to show any warnings from Wing and PyLint together in the Warnings tab, and also inline on the editor.
If this doesn't work, you can see the output of the PyLint call in the console, which you can show from the Options menu in the Command Line tool.
Please let me know you have other questions or can't get it working.