`Application` constructor should be compatible with `subprocess.Popen`

[GoogleCodeExporter]

1) What part of the model would need changes:

The `Application.__init__` constructor.

2) What is the reason why the changes is proposed:

Make the GC3Pie interface less surprising to Python programmers, who
already know the `subprocess` module.

3) What is the proposal:

The `Application.__init__` constructor should accept the same
arguments (and in the same order) as the `subprocess.Popen`
constructor. (Wherever this makes sense: for instance, we can ignore
the Windows-related stuff.)  The idea is that one can ideally replace
`subprocess.Popen` with `Application.__init__` and still get something
that works.

Original issue reported on code.google.com by riccardo.murri@gmail.com on 17 Aug 2012 at 3:06

• Blocking: #305
• Blocked on: #201, #294

[GoogleCodeExporter]

Original comment by riccardo.murri@gmail.com on 31 Aug 2012 at 10:02

• Now blocking: #305

[GoogleCodeExporter]

This entails making `inputs`, outputs` and output_dir` optional, so we need to 
decide on how to handle `output_dir` before we can fix this.

Hence, moving this forward to a new milestone.

Original comment by riccardo.murri@gmail.com on 5 Oct 2012 at 10:25

• Changed state: Started
• Added labels: Milestone-Release2.1
• Removed labels: Milestone-Release2.0