-
The outcome of the unit tests depends on the presence of the CTOOLS environment variable. If the CTOOLS environment variable is not present the unit test should fail, otherwise it sould succeed.
-
The pars() methods allow to assign or to retrieve all application parameters in a dictionary. Makes ctools a bit more "Pythonic".
-
This led to an invalid pointer problem before, is now fixed due to GammaLib fix.
-
Since the new GApplication logger methods are more compact than the old format the "logTerse()" etc. constructs have been replaced by the new logger methods. At the same time, the chattiness levels have been reviewed with the following behaviour: - TERSE: only headers - NORMAL: standard output, only main results or computations - EXPLICIT: detailed output - VERBOSE: verbose output, mainly for diagnostics
-
See #1823.
-
…or 1 (STDOUT) to /dev/null.
-
Note that test_python_ctools.py could ultimately replace all ctools, as for the shell script we anyways to not recover the results. Still, the shell script may still make some limited sense.
-
Note that this breaks compatibility with Python < 2.6.
-
This command was run: autopep8 --select E101,W191 --in-place --recursive . It fixes only these two issues: - W191 indentation contains tabs - E101 indentation contains mixed spaces and tabs
