This package contains a convenient way to invoke Python
code from the command line to execute jobs of any kind.
jobtools my_code.py my_method --arg1 value1 --arg2 true --arg3 params.yml
To run a Python
file from the command line you can do something like python task.py
, considering that you have a file called task.py
. However, if you routine needs parameters, then you have to do all the parsing of the arguments by hand. This has some limitations:
- Naming conventions in bash or Windows Command line are different. For instance parameters in bash are usually indicated as
--my-parameter
while inPython
the-
character is not valid. - Type parsing has to be done by hand with
argparser
. - It requires to handle how the file is invoked.
- Complex types are hard to indicate.
This leads to a lot of repetitive code being done each time you want to execute code in Python
from the command line. This library seeks to help to do:
- Automatic parameters parsing.
- Automatic enforcement and detection of optional parameters.
- Automatic naming convention matching (args like
--my-parameter
are passed asmy_parameter
). - Support for some complex types.
The code that you want to execute will be indicated in a callable function. Arguments for the callable are automatically parsed from the command line and enforced depending on if they are required or not. Parameters with a default value are inferred to be optional while parameters without one are marked required. Type conversion is automatically handled using type hints. Special type conversion is supported for arguments of type SimpleNamespace
which can be passed as arguments using YML
or JSON
files. Enumerators are also supported as arguments. See Using enumerators as arguments for details.
How is jobtools
different from click
?
At first, jobtools
may look very similar to click
. However, click
is intended to create command line tools using Python. That means that the code that you are writing has to be modified to meet click
requirements. You source code is coupled with the way click
works (you will import click
in your namespace, add decorators, etc). On the other hand, jobtools
is intended to be generic way to execute Python code from the command line. No modifications shall be made to the source code in order to execute the code using jobtools
(besides adding type hints). Some advance features, like enums, may be facilitated by importing jobtools
but it is not required as you can implement enumerators in your code in a native Pythonic way. Then, you code can be completely decoupled from jobtools
.
task.py
from types import SimpleNamespace
def mytask(name: str, max_buffer: int, params: SimpleNamespace, optional_arg: int = 10) -> int:
"""
This is the function you want to run
"""
...
text = f'parameters are automatically parse so I can use {name}. Since params \
is a `SimpleNamespace` argument, then the `YML` file structure will \
be mapped. I can use {params.trips.origin} and {params.trips.destiny} \
including {params.budget}.'
print(text)
return ...
Then this file can be called using the command jobtools
or pyrunit
(they are aliases):
jobtools task.py mytask --name "my name" --max-buffer 1024 --params params.yml
or
jobtools task.py mytask --name "my name" --max-buffer 1024 --params params.yml --optional-arg 15
The corresponding YML
file would be like:
params.yml
trips:
origin: 'BUE'
destiny: 'SFO'
budget: 700
Both jobtools
and pyrunit
are bash scripts installed by pipx. If you environment cannot access them because of how it is set, then you have alternatives:
-
As a
Python
module:python -m jobtools task.py MyTask --arg1 value1
-
Handling the execution yourself:
python task.py --arg1 value1
In your
Python
script add:from jobtools.runner import TaskRunner def MyMethod(arg1: str): (...) if __name__ == "__main__": tr = TaskRunner() tr.run(MyMethod)
You can use enumerators as parameters of your jobs. This results handy when you want to enforce specific values instead of handling strings as parameters. You can indicate a parameters as an enumerator using the class jobtools.arguments.StringEnum
like follows:
from types import SimpleNamespace
from jobtools.arguments import StringEnum
class CompareStrategy(StringEnum):
BIGGER_BETTER = 'Bigger is better'
SMALLER_BETTER = 'Smaller is better'
def mytask(name: str, logic: CompareStrategy = CompareStrategy.BIGGER_BETTER) -> int:
"""
This is the function you want to run
"""
...
if logic == CompareStrategy.BIGGER_BETTER:
...
return ...
Then this file can be called as:
jobtools task.py mytask --name "my name" --logic "Bigger is better"
The values in the argument logic
needs to be any of the choices in the enum indicated in the type. This is automatically enforced.
Sometimes, you code is packaged inside of a Python package or module. In the following example, assuming that you have a module that can be loaded from the path you are currently located, you can use jobtools
to run them using the following sintax:
jobtools mypkg.mymodule.mysubmod my_task --arg1 value1 --arg2 value2
The package should be resolvable from the location you are invoking the method. If it is a local package, then you should be placed outside of the package itself.
jobtools
extends the support of SimpleNamespace
in the class ParamsNamespace
which supports loading and writing configuration files directly. This is useful when authoring the configuration files in Jupyter Notebooks for instance. You can construct the configuration and save it like this:
from jobtools.arguments import ParamsNamespace
params = ParamsNamespace()
params.argument1 = 123
params.argument2 = "this is a string"
params.save('params.yml')
In the same way, loading can be done with:
from jobtools.arguments import ParamsNamespace
ParamsNamespace.load('params.yml)
Note that this functionality is added mostly for helping unit testing or fast creation of configuration files. We do not recommend loading configuration files manually, but to rely on using parameters of type
SimpleNamespace
whichjobtools
automatically map to configuration files.
You can display help about how to run an specific function by using the flag --help
or -h
. Note how argument typing help is also provided including: possible values for enums, type hints and optional vs required arguments.
> jobtools task.py mytask --help
usage: jobtools task.py mytask [-h] --integer INTEGER --decimal DECIMAL --compare-strategy {Bigger is better,Smaller is better} [--boolean BOOLEAN]
positional arguments:
task_types.py
mytask
arguments:
-h, --help show this help message and exit
--debug displays debug information about the execution
--integer INTEGER of type int
--decimal DECIMAL of type float
--compare-strategy {Bigger is better,Smaller is better}
optional arguments:
--boolean BOOLEAN of type bool
Ideas and contributions are more than welcome!