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.

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

Edge case for "none" unit conversions #567

Open
peverwhee opened this issue May 23, 2024 · 0 comments
Open

Edge case for "none" unit conversions #567

peverwhee opened this issue May 23, 2024 · 0 comments
Labels

Comments

@peverwhee
Copy link
Collaborator

Description

If a unit conversion involves "none", we get an error because "none" is a python keyword.

Steps to Reproduce

Using head of main, change the units for one instance of errmsg in one of the tests from "none" to "None"

Additional Context

We should have logic that can handle this, meaning:

  1. For "none" unit only, convert to lower case before comparing (to handle case differences)
  2. An exception to the "no python keywords allowed" rule for "none"? - so that if a user tries to convert "1" to "none" or something, they'll get a more helpful error.

Output

Error:

Invalid units entry, 'None', Python identifier, at...

Source of error: scripts/var_props.py", line 1172, in _get_unit_convstrs

@peverwhee peverwhee added the bug label May 23, 2024
peverwhee added a commit that referenced this issue Aug 7, 2024
Tiny bugfix for unit conversion edge case that was trying to convert
"None" to "none"

## Description
Convert "none" units to lowercase before comparing.

User interface changes?: No

Fixes: 
closes #567

Testing:
- Updated var_compatability_test to include a "None" to "none"
comparison

Co-authored-by: Courtney Peverley <courtneyp@derecho7.hsn.de.hpc.ucar.edu>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant