| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
Haven't look at everything nor had I marked every typo but here's a first round of comments.
Sorry, something went wrong.
Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
There was a problem hiding this comment.
Looks good, left a few comments.
General points -- the line lengths in the new text seem a bit long. Also, I wonder if it is worth covering / providing call-outs to the interactions with the annotations future? I imagine that will be something many readers will be thinking about.
A
Sorry, something went wrong.
| ``from __future__ import annotations`` was previously scheduled to | ||
| become mandatory in Python 3.10, but the Python Steering Council | ||
| twice decided to delay the change | ||
| (`announcement for Python 3.10 <https://mail.python.org/archives/list/python-dev@python.org/message/CLVXXPQ2T2LQ5MP2Y53VVQFCXYWQJHKZ/>`__; | ||
| `announcement for Python 3.11 <https://mail.python.org/archives/list/python-dev@python.org/message/VIZEBX5EYMSYIJNDBF6DMUMZOCWHARSO/>`__). | ||
| No final decision has been made yet. See also :pep:`563` and :pep:`649`. | ||
| become mandatory in Python 3.10, but the change was delayed and ultimately | ||
| canceled. This feature will eventually be deprecated and removed. See | ||
| :pep:`649` and :pep:`749`. |
There was a problem hiding this comment.
Should we provide or link to migration guidance here, especially given that this is the first time a __future__ won't become the actual future?
Sorry, something went wrong.
| The :mod:`!annotationlib` module provides tools for introspecting :term:`annotations <annotation>` | ||
| on modules, classes, and functions. |
There was a problem hiding this comment.
Potentially this could be added later, but I think a longer narrative summary of annotationlib and where it fits in could be of use -- we jump straight into functions here. Contrast with pathlib, heapq, hashlib.
I wonder if there are words from 749 that we could incorporate? Effectively, something that briefly talks to where this module fits into the landscape, perhaps aimed at the fairly experienced user of types/inspect/typing, but someone who hasn't followed the PEPs.
Sorry, something went wrong.
There was a problem hiding this comment.
Yes, I was thinking of adding that too, but ran out of energy while working on the initial version. :) I'll probably work on this later.
Sorry, something went wrong.
There was a problem hiding this comment.
I wrote such a summary now, along with a historical account of annotation semantics, since that seems like something the docs should cover.
Sorry, something went wrong.
Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
|
Doctest failures: Document: library/annotationlib
-------------------------------
**********************************************************************
File "library/annotationlib.rst", line 67, in default
Failed example:
call_evaluate_function(Alias.evaluate_value, Format.VALUE)
Exception raised:
Traceback (most recent call last):
File "/home/runner/work/cpython/cpython/Lib/doctest.py", line 1395, in __run
exec(compile(example.source, filename, "single",
~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
compileflags, True), test.globs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "<doctest default[1]>", line 1, in <module>
call_evaluate_function(Alias.evaluate_value, Format.VALUE)
~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/runner/work/cpython/cpython/Lib/annotationlib.py", line 421, in call_evaluate_function
return call_annotate_function(evaluate, format, owner=owner, _is_evaluate=True)
File "/home/runner/work/cpython/cpython/Lib/annotationlib.py", line 446, in call_annotate_function
return annotate(format)
File "<doctest default[0]>", line 1, in Alias
type Alias = undefined
^^^^^^^^^
NameError: name 'undefined' is not defined
**********************************************************************
Document: library/typing
------------------------
**********************************************************************
File "library/typing.rst", line 2181, in default
Failed example:
Alias.__value__
Exception raised:
Traceback (most recent call last):
File "/home/runner/work/cpython/cpython/Lib/doctest.py", line 1395, in __run
exec(compile(example.source, filename, "single",
~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
compileflags, True), test.globs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "<doctest default[1]>", line 1, in <module>
Alias.__value__
File "<doctest default[0]>", line 1, in Alias
type Alias = undefined
^^^^^^^^^
NameError: name 'undefined' is not defined
**********************************************************************
File "library/typing.rst", line 2185, in default
Failed example:
Alias.evaluate_value(Format.VALUE)
Exception raised:
Traceback (most recent call last):
File "/home/runner/work/cpython/cpython/Lib/doctest.py", line 1395, in __run
exec(compile(example.source, filename, "single",
~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
compileflags, True), test.globs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "<doctest default[3]>", line 1, in <module>
Alias.evaluate_value(Format.VALUE)
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
File "<doctest default[0]>", line 1, in Alias
type Alias = undefined
^^^^^^^^^
NameError: name 'undefined' is not defined
**********************************************************************
|
Sorry, something went wrong.
There was a problem hiding this comment.
Most of these are nits. I got curious about the PR and found some small things 🙈 !
Sorry, something went wrong.
There was a problem hiding this comment.
Overall, this looks good @JelleZijlstra. I'm wondering if we are going a bit too deep into implementation in the Data Model Language Reference page.
Sorry, something went wrong.
Co-authored-by: Carol Willing <carolcode@willingconsulting.com>
|
Thanks for the review @willingc! Which part do you think goes into too much detail? I looked over the data model changes and all the changes seem relevant to me. |
Sorry, something went wrong.
@JelleZijlstra I reread the data model changes again on the rendered page (instead of the diff). On the initial read, I thought there was implementation content mixed in, but I was mistaken and misled by the rST markup. Thanks for rechecking and sorry for the extra noise. Let's 🚢 this. 😄 |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
📚 Documentation preview 📚: https://cpython-previews--122235.org.readthedocs.build/