django.git/django/utils/dateformat.py, branch fix-31295django
http://cgit.adnoto.dev/django.git/atom?h=fix-312952025-07-23T23:17:55ZRefs #36500 -- Rewrapped long docstrings and block comments via a script.2025-07-23T23:17:55Zdjango-botops@djangoproject.com2025-07-23T03:41:41Zurn:sha1:69a93a88edb56ba47f624dac7a21aacc47ea474f
Rewrapped long docstrings and block comments to 79 characters + newline
using script from https://github.com/medmunds/autofix-w505.
Refs #36500 -- Shortened some long docstrings and comments.2025-07-23T23:17:55ZMike Edmundsmedmunds@gmail.com2025-07-23T03:40:48Zurn:sha1:55b0cc21310b76ce4018dd793ba50556eaf0af06
Manually reformatted some long docstrings and comments that would be
damaged by the to-be-applied autofixer script, in cases where editorial
judgment seemed necessary for style or wording changes.
Applied Black's 2024 stable style.2024-01-26T11:45:07ZMariusz Felisiakfelisiak.mariusz@gmail.com2024-01-26T11:45:07Zurn:sha1:305757aec19c9d5111e4d76095ae0acd66163e4b
https://github.com/psf/black/releases/tag/24.1.0Refs #34233 -- Referenced isocalendar() results by names not indexes.2023-01-18T11:57:54ZMariusz Felisiakfelisiak.mariusz@gmail.com2023-01-18T11:57:54Zurn:sha1:a04565845ae3e766a1a4ec827a6e1f4fac335c3a
isocalendar() returns a namedtuple() instead of tuple in Python 3.9+Simplified handling ambiguous/imaginary datetimes in django.utils.dateformat.2023-01-05T11:55:28ZNick Popenick@nickpope.me.uk2022-10-12T19:27:20Zurn:sha1:6c86495bcee22eac19d7fb040b2988b830707cbd
Instead of the separate property, we can just not set self.timezone if
the datetime is ambiguous or imaginary. This ensures that this check
will only ever happen once as it's dependant on the datetime object and
not the format string characters.
Added support for datetime.date to DateFormat.r().2023-01-05T11:51:55ZNick Popenick@nickpope.me.uk2021-05-13T12:52:18Zurn:sha1:65477fd7dae9e2c9f4a241b2eddf25bdb1ceeb0fSimplified django.utils.dateformat.DateFormat.O()/t()/e() a bit.2023-01-05T04:59:26ZNick Popenick@nickpope.me.uk2022-10-12T22:20:32Zurn:sha1:41ca2afd1ce49949d509177987c3b4b7c8ba3fa1
O() - we should try to avoid calling specifier methods from each other
to avoid extra function call overhead. In addition we end up, in this
case, duplicating the ambiguous/imaginary datetime checks. We're also
going to be looking at simplifying things by having all of these
specifier methods return strings and not an random mix of types.
t() - the value can only be one of 28, 29, 30, or 31. As such, there is
no need to zero-pad to a width of two.
Optimized imports in django.utils.dateformat.2023-01-05T04:57:50ZNick Popenick@nickpope.me.uk2022-10-12T21:45:00Zurn:sha1:d7a8ab3513dbee10a04e1f7156457b9c83754bf5
Avoid extra attribute lookup in specifier methods, etc. by importing
classes from datetime directly.
Refs #33476 -- Refactored code to strictly match 88 characters line length.2022-02-07T19:37:05ZMariusz Felisiakfelisiak.mariusz@gmail.com2022-02-04T07:08:27Zurn:sha1:7119f40c9881666b6f9b5cf7df09ee1d21cc8344Refs #33476 -- Reformatted code with Black.2022-02-07T19:37:05Zdjango-botops@djangoproject.com2022-02-03T19:24:19Zurn:sha1:9c19aff7c7561e3a82978a272ecdaad40dda5c00