[Idle-dev] Ability to integrate 3rd party code checker into IDLE

Saimadhav Heblikar saimadhavheblikar at gmail.com
Tue May 6 15:23:06 CEST 2014

I am posting an initial design plan to be able to integrate 3rd party code
checker's into IDLE.

1. UI Part
OutputWindow already has a 'goto file/line' feature, where a user can open
a file/line. This feature will be used. Depending on the 3rd party api,
there may be a need to reformat the results to match the regular
expressions of OutputWindow. Some issues like ensuring the file path is
present in the output of the 3rd party checker must be handled on a
case-to-case basis.

2.Working logic
Each 3rd party api will store its settings(IDLE related) in the same way as
extension config is stored currently(config-extensions.def), but, obviously
in a different file, meant exclusively for storing the settings for 3rd
party api settings.
It could contain details like whether it is enabled, the path/file to call
the api, the arguments to be passed etc. It could also have the details of
the function to be called if there is need for reformatting.
The location and name of the config file is to be discussed.

With these settings in place, subprocess.Popen will be used to run the 3rd
party code checker and send the result to an OutputWindow instance
with/without reformattting.

http://bugs.python.org/issue3068 provides option to modify config via GUI.
This could be used for the current purpose as well.

While we could add support for as many 3rd party code checkers, there is a
need to document the process to enable others to integrate their
extensions. This will be done once things are ready.
If i missed out something i will reply to this thread.

Looking forward to your comments and feedback.

Saimadhav Heblikar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/idle-dev/attachments/20140506/f9d3359a/attachment.html>

More information about the IDLE-dev mailing list