Verbosity for pipeline_printout and pipeline_run is a mess

[GoogleCodeExporter]

Verbosity levels for pipeline_printout and pipeline_run do not seem to be 
synchronised. It is not clear what exactly increasing verbosity does at each 
level. What is more, different things seem to happen differently at run time 
and print_out. 

verbosity =
1) Out-of-date Tasks
2) All Tasks
3) Out-of-date Jobs in Out-of-date Tasks 
4) All Jobs in Out-of-date Tasks 
5) All jobs in All Tasks whether out of date or not

path_verbosity = 
(default = 2)

0) the full path
1-N) N levels of subpath, 
    for "what/is/this.txt"
    N = 1 "this.txt"
    N = 2 "is/this.txt"
    N >=3 "what/is/this.txt"
-N) As above but with the input/output parameter chopped off after 40 letters,
    and ending in "..."

Original issue reported on code.google.com by bunbu...@gmail.com on 14 May 2014 at 10:23

[GoogleCodeExporter]

Getting the Nth levels of a path use code from ruffus.ruffus_utility

from ruffus.ruffus_utility import *
for aa in range(10):
   print get_nth_nested_level_of_path ("/test/this/now/or/not.txt", aa)

Original comment by bunbu...@gmail.com on 15 May 2014 at 4:07

[GoogleCodeExporter]

1) pipeline_printout forwards printing to _task.printout
2) pipeline_run needs to borrow code from pipeline_printout to print up to date 
tasks including their jobs
3) See file_name_parameters.py::get_readable_path_str()

Original comment by bunbu...@gmail.com on 29 May 2014 at 7:00

[GoogleCodeExporter]

Will be in version 2.5. See github

Original comment by bunbu...@gmail.com on 24 Jul 2014 at 6:59

• Changed state: Verified