summaryrefslogtreecommitdiffstats
path: root/Lib/sqlite3
diff options
context:
space:
mode:
authorPaul Ganssle <paul@ganssle.io>2020-05-16 14:02:59 (GMT)
committerGitHub <noreply@github.com>2020-05-16 14:02:59 (GMT)
commit1b97b9b0ad9a2ff8eb5c8f2e2e7c2aec1d13a330 (patch)
treee4e0db3789e402a65ad817f0a17375b756d3e251 /Lib/sqlite3
parentaa92a7cf210c98ad94229f282221136d846942db (diff)
downloadcpython-1b97b9b0ad9a2ff8eb5c8f2e2e7c2aec1d13a330.zip
cpython-1b97b9b0ad9a2ff8eb5c8f2e2e7c2aec1d13a330.tar.gz
cpython-1b97b9b0ad9a2ff8eb5c8f2e2e7c2aec1d13a330.tar.bz2
bpo-24416: Return named tuple from date.isocalendar() (GH-20113)
{date, datetime}.isocalendar() now return a private custom named tuple object IsoCalendarDate rather than a simple tuple. In order to leave IsocalendarDate as a private class and to improve what backwards compatibility is offered for pickling the result of a datetime.isocalendar() call, add a __reduce__ method to the named tuples that reduces them to plain tuples. (This is the part of this PR most likely to cause problems — if it causes major issues, switching to a strucseq or equivalent would be prudent). The pure python implementation of IsoCalendarDate uses positional-only arguments, since it is private and only constructed by position anyway; the equivalent change in the argument clinic on the C side would require us to move the forward declaration of the type above the clinic import for whatever reason, so it seems preferable to hold off on that for now. bpo-24416: https://bugs.python.org/issue24416 Original PR by Dong-hee Na with only minor alterations by Paul Ganssle. Co-authored-by: Dong-hee Na <donghee.na92@gmail.com>
Diffstat (limited to 'Lib/sqlite3')
0 files changed, 0 insertions, 0 deletions