summaryrefslogtreecommitdiffstats
path: root/Python
diff options
context:
space:
mode:
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>2024-01-29 09:46:48 (GMT)
committerGitHub <noreply@github.com>2024-01-29 09:46:48 (GMT)
commitd14003adf267dc09f5a245235ad1fc25888b8848 (patch)
tree7342862b1f858c785839f1d462197595bad71fd5 /Python
parente60435813cafd6b20d02437c63212e33a963aaf8 (diff)
downloadcpython-d14003adf267dc09f5a245235ad1fc25888b8848.zip
cpython-d14003adf267dc09f5a245235ad1fc25888b8848.tar.gz
cpython-d14003adf267dc09f5a245235ad1fc25888b8848.tar.bz2
[3.12] gh-110893: Improve the documentation for __future__ module (GH-114642) (#114702)
gh-110893: Improve the documentation for __future__ module (GH-114642) nedbat took issue with the phrasing "real module". I'm actually fine with that phrasing, but I do think the `__future__` page should be clear about the way in which the `__future__` module is special. (Yes, there was a footnote linking to the future statements part of the reference, but there should be upfront discussion). I'm sympathetic to nedbat's claim that no one really cares about `__future__._Feature`, so I've moved the interesting table up to the top. (cherry picked from commit 3b86891fd69093b60141300862f278614ba80613) Co-authored-by: Shantanu <12621235+hauntsaninja@users.noreply.github.com>
Diffstat (limited to 'Python')
0 files changed, 0 insertions, 0 deletions