You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/monthly-meeting/2023-12.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,9 +32,9 @@ Please take a second to read through it!
32
32
*[Ryan] standard library documentation reference and adding types to it in a structured way. For example, `collections.Counter.most_common` could be written
33
33
34
34
most_common(n: int) -> list[tuple[Any, int]]
35
-
35
+
36
36
[Petr] ... or `list[tuple[KeyType, int]]`?
37
-
37
+
38
38
- this has been discussed. There was opposition to adding the types to the stdlib code itself.
39
39
-[JDLH] I sometimes wish for more normative, less chatty module documentation. e.g. [*heapq* module](https://docs.python.org/3/library/heapq.html). e.g. old issue 29428 [*Doctest documentation unclear about multi-line fixtures*](https://bugs.python.org/issue29428).
40
40
@@ -69,7 +69,7 @@ Please take a second to read through it!
69
69
* There are some "easy" issues, although they can occasionally not be actually-easy.
70
70
* Interested in documentation, look at diataxis and make changes?
0 commit comments