subprocess shouldn't be used, except inside plugins

Registered by Loïc Grobol on 2012-07-17

From the very beginning cteslo has been using subprocess.Popen and his siblings (call…) for plugin use. This is messy at best and makes several features like logging, graceful error management impossible. Thus the need to move all this to a cleaner flow: plugins will now need a script in python3 (as is already the case anyway), that will be either the plugin's engine or an adapter for a binary plugin (in this case, the adapter should use subprocess). This script will be used by libcteslo directly via internal python, that is, either runpy or import, though the latter may be better.

Blueprint information

Status:
Started
Approver:
Loïc Grobol
Priority:
Essential
Drafter:
Loïc Grobol
Direction:
Approved
Assignee:
Loïc Grobol
Definition:
Approved
Series goal:
None
Implementation:
Good progress
Milestone target:
None
Started by
Loïc Grobol on 2012-09-14

Related branches

Sprints

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.