[maoxor]

Python 3.14 removed the deprecated ast.Str and ast.Ellipsis aliases, and py2pyi still uses them in _is_empty_class and _body_ellip. As a result, py2pyi fails on 3.14 for any module with a function docstring:

  File ".../fastcore/py2pyi.py", line 147, in _body_ellip
    stidx = 1 if isinstance(n.body[0], ast.Expr) and isinstance(n.body[0].value, ast.Str) else 0
AttributeError: module 'ast' has no attribute 'Str'

This checks for ast.Constant with a str (or ...) value instead. That's exactly what the aliases' isinstance matched on 3.8 to 3.13. The change is in the notebook, and fastcore/py2pyi.py is regenerated with nbdev-export; only those two lines change. I also removed the cell outputs that contained only the ast.Str is deprecated / ast.Ellipsis is deprecated warnings, since they no longer happen.

Tests: the existing cells in 10_py2pyi.ipynb already catch this, but only on 3.14, which CI doesn't run (3.10 to 3.13).

• nbdev-test nbs/10_py2pyi.ipynb on 3.14: fails on main with AttributeError: module 'ast' has no attribute 'Ellipsis', and passes with this change. On 3.13 it passes both ways. 06_script.ipynb, which mentions py2pyi, passes on 3.14 too.
• On 3.13, where the aliases still exist, I compared old and new checks on 14 nodes: str, ..., int, None, bytes and bool constants, a Name, an f-string, a call, and the same parsed from source. They agree on all of them.
• End to end, I ran py2pyi on a small module with a docstring-only class, a class X: ..., a class with a documented method and a @patched method. The .pyi from this branch on 3.13 and 3.14 is byte-identical to main's on 3.13.