e.g., mg/l vs mg/L is handled fine by pint, but any pre-processing that updates unit-string to fix it before pint works with it have to recognize/fix both. Planned solution is either (A) upper()/lower() and make sure it doesn't change the meaning to pint, OR (B) use upper lower to build out the dict/list (not preferable because string may be longer than char that is problematic and could require many combinations). TADA uses all caps for this and other fields.
e.g., mg/l vs mg/L is handled fine by pint, but any pre-processing that updates unit-string to fix it before pint works with it have to recognize/fix both. Planned solution is either (A) upper()/lower() and make sure it doesn't change the meaning to pint, OR (B) use upper lower to build out the dict/list (not preferable because string may be longer than char that is problematic and could require many combinations). TADA uses all caps for this and other fields.