-
Notifications
You must be signed in to change notification settings - Fork 18
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
Wrongfully recognition with %m/%d/%y #74
Comments
I am not sure what you are expecting. If you have an obscure new format, use As for I plan to close this unless you manage to convince that there is shortcoming in |
Also R> library(anytime)
R> anytime::addFormats("%m/%d/%y %H:%M:%S")
R> anytime("03/04/05 06:07:08")
[1] "2005-03-04 06:07:08 CST"
R> So I am not sure what the question is here. |
I think |
Yes, while writing it I realized you may "simply" have confused the formats between And yes, executive decision at my end to prefer four-digit years so the default formats are all with |
I want to convert strings that are formatted as such
01/15/17
(January 15th 2017). But when I add the%m/%d/%y
formats, it recognises random strings as date.Interestingly, it seems like many characters are actually ignored.
Is there another more specific format I could use?
The text was updated successfully, but these errors were encountered: