cdo-bindings
cdo-bindings copied to clipboard
Ruby/Python bindings for CDO
This seems to fix the issue where kill/interrupt signals outside of the cdo binding are suppressed mentioned in #26 and #43. It also fixed a few quick-to-repair issues I came...
Collecting package metadata (current_repodata.json): done Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source. Collecting package metadata (repodata.json): done Solving environment: failed PackagesNotFoundError: The following packages...
Python binding captures "kill" and "KeyboardInterrupt" signals in all processes after initialization
Attempting to interrupt a process with Ctrl-C after initializing the python binding with `cdo = Cdo()` often fails and prints weird messages, even when interrupting python processes unrelated to the...
Running a process with a `Cdo()` interface instantiated in a python module does not allow for a `ctrl-C` exit. This is likely a problem with the signal handling. It looks...
just realized this yesterday. might be that the new interface, i.e. cdo. is callable and returns another Cdo object interferes with the definition of help() found in cdo.py 1.5.4
kick travisCI and ise github workflows for ruby testing
#35 did not trigger a build - no idea why
With the new syntax ```cdo.op1().op2().op3().run()``` the question comes up: How to handle operators with multiple inputs. Here is one idea I'd like to discuss @Chilipp ``` cdo -add -fldmean -topo,global_0.2...
When cdo is not on the users path or when the cdo to be used is different, the version 1.6.0 will not work. This was not a problem with v1.5.x....
While reading the README I spotted a couple of typos which I thought you'd like to have fixed. I also spotted an extra comma and some trailing whitespace which you...