/Mac/Modules/cf/

n value='3.3'>3.3 https://github.com/python/cpython.git
summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* [3.11] gh-101100: Fix class reference in library/test.rst (GH-114769) ↵Miss Islington (bot)2024-01-311-1/+1
| | | | | | | | | | (GH-114793) The text clearly seems to be referencing `TestFuncAcceptsSequencesMixin`, for which no target is available. Name the class properly and suppress the dangling reference. (cherry picked from commit 7a93db44257c0404dc407ff2ddc997f4bb8890ed) Co-authored-by: Skip Montanaro <skip.montanaro@gmail.com>
* [3.11] gh-101100: Fix references in csv docs (GH-114658) (GH-114773)Skip Montanaro2024-01-312-8/+7
| | | | | Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> (cherry picked from commit 3911b42cc0d404e0eac87fce30b740b08618ff06)
* [3.11] Docs: mark up dbm.gnu.open() and dbm.ndbm.open() using param list ↵Miss Islington (bot)2024-01-311-61/+56
| | | | | | | (GH-114762) (#114784) (cherry picked from commit c8cf5d7d148944f2850f25b02334400dd0238cb0) Co-authored-by: Erlend E. Aasland <erlend@python.org>
* gh-110190: Fix ctypes structs with array on Windows ARM64 (GH-114753)Miss Islington (bot)2024-01-312-1/+2
| | | | | (cherry picked from commit a06b606462740058b5d52fefdcdcd679d4f40260) Co-authored-by: Diego Russo <diego.russo@arm.com>
* [3.11] Clarify one-item tuple (GH-114745) (#114758)Miss Islington (bot)2024-01-301-2/+3
| | | | | | | A 'single tuple' means 'one tuple, of whatever length. Remove the unneeded and slightly distracting parenthetical 'singleton' comment. (cherry picked from commit a1332a99cf1eb9b879d4b1f28761b096b5749a0d) Co-authored-by: Terry Jan Reedy <tjreedy@udel.edu>
* [3.11] Set `hosted_on` for Read the Docs builds (GH-114697) (#114735)Miss Islington (bot)2024-01-291-18/+19
| | | | Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
* [3.11] Fix more references to datetime and time classes (GH-114717) (GH-114726)Serhiy Storchaka2024-01-293-8/+8
| | | | They could be confused with references to datetime and time modules. (cherry picked from commit 39c766b579cabc71a4a50773d299d4350221a70b)
* [3.11] Remove limit in calendar CLI help message for year arg (GH-114719) ↵Miss Islington (bot)2024-01-291-1/+1
| | | | | | | | (GH-114723) The limit was removed in 66c88ce30ca2b23daa37038e1a3c0de98f241f50 (GH-4109). (cherry picked from commit 0f54ee4c6cdba74492183eb2dd142393c7dba403) Co-authored-by: Steven Ward <planet36@users.noreply.github.com>
* [3.11] gh-101100: Fix datetime reference warnings (GH-114661) (GH-114718)Serhiy Storchaka2024-01-293-54/+58
| | | | | (cherry picked from commit e8b8f5e9c2da6a436360ce648061c90bdfcba863) Co-authored-by: Skip Montanaro <skip.montanaro@gmail.com>
* [3.11] gh-89159: Add some TarFile attribute types (GH-114520) (GH-114715)Miss Islington (bot)2024-01-291-0/+6
| | | | | (cherry picked from commit d7d0d13cd37651990586d31d8974c59bd25e1045) Co-authored-by: Stanley <46876382+slateny@users.noreply.github.com>
* [3.11] gh-101100: Fix Sphinx warnings in `whatsnew/2.2.rst` (GH-112366) ↵Miss Islington (bot)2024-01-292-71/+70
| | | | | | | (#114712) Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
* [3.11] gh-114685: Fix incorrect use of PyBUF_READ in import.c (GH-114686) ↵Miss Islington (bot)2024-01-291-1/+1
| | | | | | | (GH-114701) (cherry picked from commit 1ac1b2f9536a581f1656f0ac9330a7382420cda1) Co-authored-by: Nikita Sobolev <mail@sobolevn.me>
* [3.11] gh-101100: Fix sphinx warnings in `Doc/c-api/memoryview.rst` ↵Miss Islington (bot)2024-01-292-1/+13
| | | | | | | (GH-114669) (GH-114705) (cherry picked from commit 97fb2480e4807a34b8197243ad57566ed7769e24) Co-authored-by: Nikita Sobolev <mail@sobolevn.me>
* [3.11] gh-110893: Improve the documentation for __future__ module ↵Miss Islington (bot)2024-01-291-42/+56
| | | | | | | | | | | | | | | | | | (GH-114642) (#114703) 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>
* [3.11] Correct Skip Montanaro's email address (GH-114677) (#114680)Miss Islington (bot)2024-01-284-5/+5
| | | | | | Correct Skip Montanaro's email address (GH-114677) (cherry picked from commit 5ecfd750b4f511f270c38f0d748da9cffa279295) Co-authored-by: Skip Montanaro <skip.montanaro@gmail.com>
* [3.11] gh-114100: Remove superfluous writing to fd 1 in test_pty (GH-114647) ↵Miss Islington (bot)2024-01-27