Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Using environment setting in a single cdo call is not supported #8

Closed
Try2Code opened this issue Jul 8, 2016 · 1 comment
Closed

Using environment setting in a single cdo call is not supported #8

Try2Code opened this issue Jul 8, 2016 · 1 comment
Assignees
@Try2Code

Comments

@Try2Code
Copy link
Owner

Try2Code commented Jul 8, 2016

In the current release 1.3.0 the ruby version does not support the assignment of environment variables per call, only as a object setup, i.e.

cdo.env = {"PLANET_RADIUS" => "6379000"}

works, but

cdo.fldmean(input: ..., env: {"PLANET_RADIUS" => "6379000"}

doesn't

the test (test_env) does not cover this feature, because it is testing for the default parameter values
@Try2Code Try2Code self-assigned this Jul 8, 2016
Try2Code added a commit that referenced this issue Jul 11, 2016
@Try2Code
improve testing for env handling (python) #8
16f42fa
Try2Code added a commit that referenced this issue Jul 11, 2016
@Try2Code
fix env handling (ruby) #8
d408711
Try2Code added a commit that referenced this issue Jul 11, 2016
@Try2Code
new cdo.rb release 1.3.1: bugfix #8 - class interface only!
51069ad
@Try2Code
Copy link
Owner Author

bugfix relased on rubygems

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Try2Code Try2Code

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Try2Code