Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fixes two typos in whatsnew v8 #14290

Merged
merged 1 commit into from Jan 14, 2024
Merged

Fixes two typos in whatsnew v8 #14290

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/source/whatsnew/version8.rst
View file
Open in desktop
Expand Up @@ -346,7 +346,7 @@ SPEC 0 and SPEC 4
You've heard about the NEPs, (NumPy enhancement Proposal), having a NEP for something non-numpy specific was sometime confusing.
Long live the `SPECs <https://scientific-python.org/specs/>`_.

We are now trying to follow SPEC 0 (aka old NEP 29) for of support of upstream libraries.
We are now trying to follow SPEC 0 (aka old NEP 29) for support of upstream libraries.

We also now try to follow SPEC 4 (test and publish nightly on a centralized nightly repository).
We encourage you to do so as well in order to report breakage, and contribute to the SPEC process !
Expand All @@ -356,7 +356,7 @@ Python 3.12 compatibility ?
~~~~~~~~~~~~~~~~~~~~~~~~~~~

Python 3.12 changed its tokenizer to have better support for f-strings and allow arbitrary expression.
This is a great new feature and performance improvement in python 3.12.
This is a great new feature and performance improvement in Python 3.12.

Unfortunately this means the new tokenizer does not support incomplete or invalid Python which will
break many features of IPython. Thus compatibility of IPython with Python 3.12 is not guarantied.
Expand Down