##// END OF EJS Templates
whats new 8.14 (#14092)
Matthias Bussonnier -
r28316:a3ede0d8 merge
parent child Browse files
Show More
@@ -1,6 +1,51 b''
1 ============
1 ============
2 8.x Series
2 8.x Series
3 ============
3 ============
4 .. _version 8.14:
5
6 IPython 8.14
7 ------------
8
9 Small release of IPython.
10
11 - :ghpull:`14080` fixes some shortcuts issues.
12 - :ghpull:`14056` Add option to ``%autoreload`` to hide errors when reloading code. This will be the default for spyder
13 user is my understanding.
14 - :ghpull:`14039` (and :ghpull:`14040`) to show exception notes in tracebacks.
15
16 - :ghpull:`14076` Add option to EventManager to prevent printing
17
18
19 SPEC 0 and SPEC 4
20 ~~~~~~~~~~~~~~~~~
21
22 You've heard about the NEPs, (NumPy enhancement Proposal), having a NEP for something non-numpy specific was sometime confusing.
23 Long live the `SPECs <https://scientific-python.org/specs/>`_.
24
25 We are now trying to follow SPEC 0 (aka old NEP 29) for of support of upstream libraries.
26
27 We also now try to follow SPEC 4 (test and publish nightly on a centralized nightly repository).
28 We encourage you to do so as well in order to report breakage, and contribute to the SPEC process !
29
30
31 Python 3.12 compatibility ?
32 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
33
34 Python 3.12 changed its tokenizer to have better support for f-strings and allow arbitrary expression.
35 This is a great new feature and performance improvement in python 3.12.
36
37 Unfortunately this means the new tokenizer does not support incomplete or invalid Python which will
38 break many features of IPython. Thus compatibility of IPython with Python 3.12 is not guarantied.
39 It is unclear to which extent IPython is affected, and whether we can/should try to still support magics, shell
40 escape (``! ....``), ..., as well as how to do it if we can.
41
42 In addition even if we there is technical feasibility to do so, it is no clear we have the resources to do it.
43 We are thus looking for your help if you can _test_ on Python 3.12 to see to which extent this affects users and which
44 features are critical.
45
46 We are not going to pin IPython to Python ``<3.12`` as otherwise on install pip would downgrade/resolve to IPython 8.13,
47 so if you plan to update to Python 3.12 after its release, we encourage for extra care.
48
4
49
5 .. _version 8.13.1:
50 .. _version 8.13.1:
6 .. _version 8.13.2:
51 .. _version 8.13.2:
@@ -10,12 +55,12 b' IPython 8.13.1, 8.13.2 and 8.12.2'
10 ---------------------------------
55 ---------------------------------
11
56
12 3 quick in succession patch release of IPython in addition to IPython 8.13.0
57 3 quick in succession patch release of IPython in addition to IPython 8.13.0
13 having been yanked.
58 having been yanked.
14
59
15 IPython 8.13.0 was improperly tagged as still compatible with Python 3.8, and
60 IPython 8.13.0 was improperly tagged as still compatible with Python 3.8, and
16 still had some mention of compatibility woth 3.8. IPython 8.13.1 is identical to
61 still had some mention of compatibility woth 3.8. IPython 8.13.1 is identical to
17 8.13 but with the exception of being correctly tagged. This release and yank was
62 8.13 but with the exception of being correctly tagged. This release and yank was
18 mostly done to fix CI.
63 mostly done to fix CI.
19
64
20 IPython 8.12.2 and 8.13.2 contain UI fixes, with respect to right arrow not
65 IPython 8.12.2 and 8.13.2 contain UI fixes, with respect to right arrow not
21 working in some case in the terminal, and 8.12.2 contain also a requested
66 working in some case in the terminal, and 8.12.2 contain also a requested
General Comments 0
You need to be logged in to leave comments. Login now