Changes between Initial Version and Version 1 of Ticket #29600
- Timestamp:
- Jul 26, 2018, 1:52:21 PM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #29600 – Description
initial v1 1 1 `django.utils.datetime_safe` was added in #1443 to overcome limitations in Python 2.7 where `strftime()` doesn't support dates with year < 1900. That issue is fixed in Python 3, but an issue remains where the result of `strftime('%Y')` [https://bugs.python.org/issue13305 isn't consistent] across all platforms. That issue was worked around in #12524. 2 2 3 `strftime()` is no longer used in the JSON serializer as of 9b1cb755a28f020e27d4268c214b25315d4de42e, so using `datetime_safe()` is obsolete there.3 `strftime()` and `datetime_safe` are no longer used in the JSON serializer as of 9b1cb755a28f020e27d4268c214b25315d4de42e but the fix from 03924929ba212368240bd7a26b14208fba965cb9 may still be useful in the other places that `datetime_safe` is used. 4 4 5 If we remove `dateteime_safe` usage in migrations (it 's need is questionable), that would fix #29595.5 If we remove `dateteime_safe` usage in migrations (its need there is questionable, I think), that would fix #29595.