modularise job creation code
-
bilby_pipe.main
is getting very large (>1000 lines of code) and has a lot going on - this MR moves the condor/slurm job creation code into a separate module
If the above is considered a good idea, I am also happy to add docs to the new files that have been created.
Merge request reports
Activity
- Automatically resolved by Avi Vajpeyi
@avi.vajpeyi, I think this is a positive change.
It might be a good idea to keep copies of the moved classes in the
main
module with a deprecation warning, at least for a release or two.FWIW, I'd be okay with not adding the deprecation warning. I don't think anyone is using bilby_pipe as an API or doing such an import. On the other hand, it is an extra thing to maintain (we eventually need to phase it out). So long as the CHANGELOG is clear, breaking changes are okay right now.
Woohoo! Fewer changes for me to make :)
I'd like to side with Greg on not adding the deprecation warning.
Are you ok with that @colm.talbot ?
mentioned in issue bilby#509 (closed)
mentioned in commit ade6e0b1
changed milestone to %1.0.1