Closed lbesnard closed 8 years ago
Hi @lbesnard, it looks like this may be fixed already in a dependent library, ioos/petulant-bear#4, which I've just noticed has not had a release with that fix in it. That'll happen soon I suppose.
In the mean time, try updating your petulant-bear library to use the latest master and see if that gets you further.
Activate your environment and pip install --upgrade git+git://github.com/ioos/petulant-bear.git
- this command may need tweaking.
Thanks @daf . @danfruehauf do you think you could update this on the testing env ?
I'll be publishing a new version of petulant bear next week.
@lukecampbell poke!
Thanks @lukecampbell , that seems to fix the encoding problems we've been seeing.
Should petulant-bear v0.1.3 be added to the requirements.txt file, or will one of the other packages listed there depend on this new version?
@mhidas, Wicken depends on it and will pull in the latest version on a new install, but should also be adjusted and a new version released, and then this requirements.txt bumped as well to reflect that. That would ensure proper propagation. Leaving this open until that happens.
Fixed with the unicode changes
G'Day, I'm taking over @mhidas for a couple of weeks.
When running the ncchecker with -t=cf on this specific file :
I get the following output:
I'm using the latest commit of the master branch https://github.com/aodn/compliance-checker/commit/99b30ddb398e24991a5ba79dae8bc65771acdf71
The checker works fine with other files (which works fine with ncdump).
thanks