-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Why are we doing second -> date conversion our selves? #2845
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
Comments
This should probably be dealt with while fixing #2294. |
I'm not seeing exactly what you are talking about with this. Has it already been fixed? L350 of strftime in the current version is L434-L466, but I don't see anything obviously wrong with it. |
I no longer remember what prompted me to create this issue. I think it boils down to the fact that we have all manner of logic for converting dates <-> scalars that should be handled by an external library. Closing this as the fix is probably a complete overhaul of dates which is sort of already on the radar. |
Well with regards to the question of
|
See ~L350 in
matplotlib.dates.py
instrftime
. Without delving too deep, I think this should be handled bydatetime
.The text was updated successfully, but these errors were encountered: