-
-
Notifications
You must be signed in to change notification settings - Fork 6.1k
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
ArrowParseWarnings - turning to errors in 0.15.0 #2126
Comments
I already grepped for it for a first glance... |
seems like the warnings will stay for all string-parsing, no matter if it's supported in 0.15.0 or not (so it's not showing us where we're doing something non-supported) Parsing integers (like Also all supported date-formats remain there (and we don't use anything exotic afaik) - so i'm not sure if we need to act. We'll however need to do testing once 0.15.0 hits. |
in |
Have not found any suspicious yet. (grepped for I wanted to post here the whole list of appearances where |
This has now landed - and i ran through all modes we have and didn't find any issues, so i'll close this issue now. |
Describe your environment
Step 3: Related logs
we'll need to find all
arrow.get()
calls which don't use one of the supported formats (see github issue arrow-py/arrow#612) for more details.The text was updated successfully, but these errors were encountered: