-
Notifications
You must be signed in to change notification settings - Fork 19
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
Wierd behaviour by cf-dump #770
Comments
Thanks for reporting, Bryan. I have seen some such warnings recently elsewhere (not from cfa but in cf-python within interactive Python) and from that I believe they only emerge at Python 3.12, or at least much newer versions of Python. They are definitely not emerging in Python 3.8, at least in the separate cases that raise them I observed (which may be the same ultimate origin). We will investigate. FYI we have some other harmless warnings being raised (see NCAS-CMS/cfdm#293) that we are overdue to get removed from spamming the user. Hopefully I can find some time and fix both of these at once. |
Hi @bnlawrence, I'm a bit stumped, because that line in Removing all of the |
Hi @sadielbartholomew, I've tested NCAS-CMS/cfdm#292 ( |
OK, here it is, I think (https://docs.python.org/3/whatsnew/3.12.html#other-language-changes):
So, some more general work is probably needed on this. |
The weird thing about this is that were was no |
I see what you mean, but rest assured that the problem is purely within strings embedded in the library code :) |
Sure, I have just tested this and noted it on the PR (seemed like a more relevant place to submit comments, given it concerns the specific branch, not just the issue at hand). |
The output of cf-dump seems to be seeing some sort of escaping and not liking it. Problem manifests in a docker container (you can use the
atmbnl/datatools
container to see it?So it doesn't like it, then does the right thing ... so the bug is the spurious warning error message!
Environment:
(But this is the "special" version using
)
The text was updated successfully, but these errors were encountered: