RF: move script running code into own module #418
Conversation
Refactor code to run scripts into own module. In fact I'm using a version I refactored for another project, to make it easier to use across projects, but I think this makes the code easier to read and support.
Python 3.2 does not set __package__; work around for now.
I tend to think of directories nearer root as being 'down', it looks more common to think of this as being 'up', change according to Ariel's suggestion.
|
Cool. Did you decide against the Travis reorg? For future reference, is this the relevant commit on nipy? |
|
I thought I would work round the problem for now. Here's my WIP for moving to the more standard build system: #428 |
|
Cool. How about we hold off on this, until we resolve the Travis stuff? On Wed, Oct 1, 2014 at 9:09 AM, Matthew Brett notifications@github.com
|
|
OK - seems like we will need this anyway, considering that we might keep supporting 3.2, so I am going to go ahead and merge this. |
|
Thanks for the review... On 10/6/14, Ariel Rokem notifications@github.com wrote:
|
RF: move script running code into own module
Refactor code to run scripts into own module. In fact I'm using a version I
refactored for another project, to make it easier to use across projects, but
I think this makes the code easier to read and support.