Show More
@@ -11,7 +11,7 This document describes in-flight development work. | |||||
11 | `docs/source/whatsnew/pr` folder |
|
11 | `docs/source/whatsnew/pr` folder | |
12 |
|
12 | |||
13 |
|
13 | |||
14 |
Released .... ...., 201 |
|
14 | Released .... ...., 2019 | |
15 |
|
15 | |||
16 |
|
16 | |||
17 | Need to be updated: |
|
17 | Need to be updated: | |
@@ -22,71 +22,10 Need to be updated: | |||||
22 |
|
22 | |||
23 | pr/* |
|
23 | pr/* | |
24 |
|
24 | |||
25 |
|
||||
26 |
|
||||
27 | Prompt Rendering Performance improvements |
|
|||
28 | ========================================= |
|
|||
29 |
|
||||
30 | Pull Request :ghpull:`11933` introduced an optimisation in the prompt rendering |
|
|||
31 | logic that should decrease the resource usage of IPython when using the |
|
|||
32 | _default_ configuration but could potentially introduce a regression of |
|
|||
33 | functionalities if you are using a custom prompt. |
|
|||
34 |
|
||||
35 | We know assume if you haven't changed the default keybindings that the prompt |
|
|||
36 | **will not change** during the duration of your input – which is for example |
|
|||
37 | not true when using vi insert mode that switches between `[ins]` and `[nor]` |
|
|||
38 | for the current mode. |
|
|||
39 |
|
||||
40 | If you are experiencing any issue let us know. |
|
|||
41 |
|
||||
42 | Code autoformatting |
|
|||
43 | =================== |
|
|||
44 |
|
||||
45 | The IPython terminal can now auto format your code just before entering a new |
|
|||
46 | line or executing a command. To do so use the |
|
|||
47 | ``--TerminalInteractiveShell.autoformatter`` option and set it to ``'black'``; |
|
|||
48 | if black is installed IPython will use black to format your code when possible. |
|
|||
49 |
|
||||
50 | IPython cannot always properly format your code; in particular it will |
|
|||
51 | auto formatting with *black* will only work if: |
|
|||
52 |
|
||||
53 | - Your code does not contains magics or special python syntax. |
|
|||
54 |
|
||||
55 | - There is no code after your cursor. |
|
|||
56 |
|
||||
57 | The Black API is also still in motion; so this may not work with all versions of |
|
|||
58 | black. |
|
|||
59 |
|
||||
60 | It should be possible to register custom reformatter, though the API is till in |
|
|||
61 | flux. |
|
|||
62 |
|
||||
63 | Arbitrary Mimetypes Handing in Terminal |
|
|||
64 | ======================================= |
|
|||
65 |
|
||||
66 | When using IPython terminal it is now possible to register function to handle |
|
|||
67 | arbitrary mimetypes. While rendering non-text based representation was possible in |
|
|||
68 | many jupyter frontend; it was not possible in terminal IPython, as usually |
|
|||
69 | terminal are limited to displaying text. As many terminal these days provide |
|
|||
70 | escape sequences to display non-text; bringing this loved feature to IPython CLI |
|
|||
71 | made a lot of sens. This functionality will not only allow inline images; but |
|
|||
72 | allow opening of external program; for example ``mplayer`` to "display" sound |
|
|||
73 | files. |
|
|||
74 |
|
||||
75 | So far only the hooks necessary for this are in place, but no default mime |
|
|||
76 | renderers added; so inline images will only be available via extensions. We will |
|
|||
77 | progressively enable these features by default in the next few releases, and |
|
|||
78 | contribution is welcomed. |
|
|||
79 |
|
||||
80 | We welcome any feedback on the API. See :ref:`shell_mimerenderer` for more |
|
|||
81 | informations. |
|
|||
82 |
|
||||
83 | This is originally based on work form in :ghpull:`10610` from stephanh42 |
|
|||
84 | started over two years ago, and still a lot need to be done. |
|
|||
85 |
|
||||
86 | .. DO NOT EDIT THIS LINE BEFORE RELEASE. FEATURE INSERTION POINT. |
|
25 | .. DO NOT EDIT THIS LINE BEFORE RELEASE. FEATURE INSERTION POINT. | |
87 |
|
26 | |||
88 |
|
27 | |||
89 | Backwards incompatible changes |
|
28 | Backwards incompatible changes | |
90 | ------------------------------ |
|
29 | ------------------------------ | |
91 |
|
30 | |||
92 | .. DO NOT EDIT THIS LINE BEFORE RELEASE. INCOMPAT INSERTION POINT. No newline at end of file |
|
31 | .. DO NOT EDIT THIS LINE BEFORE RELEASE. INCOMPAT INSERTION POINT. |
@@ -2,8 +2,104 | |||||
2 | 7.x Series |
|
2 | 7.x Series | |
3 | ============ |
|
3 | ============ | |
4 |
|
4 | |||
|
5 | IPython 7.10.0 | |||
|
6 | ============== | |||
|
7 | ||||
|
8 | IPython 7.10 is the first double digit minor release in the last decade, and | |||
|
9 | first since the release of IPython 1.0, previous double digit minor release was | |||
|
10 | in August 2009. | |||
|
11 | ||||
|
12 | We've been trying to give you regular release on the last Friday of every month | |||
|
13 | for a guaranty of rapid access to bug fixes and new features. | |||
|
14 | ||||
|
15 | Unlike the previous first few releases that have seen only a couple of code | |||
|
16 | changes, 7.10 bring a number of changes, new features and bugfixes. | |||
|
17 | ||||
|
18 | Stop Support for Python 3.5 – Adopt NEP 29 | |||
|
19 | ------------------------------------------ | |||
|
20 | ||||
|
21 | IPython has decided to follow the informational `NEP 29 | |||
|
22 | <https://numpy.org/neps/nep-0029-deprecation_policy.html>`_ which layout a clear | |||
|
23 | policy as to which version of (C)Python and NumPy are supported. | |||
|
24 | ||||
|
25 | We thus dropped support for Python 3.5, and cleaned up a number of code path | |||
|
26 | that were Python-version dependant. If you are on 3.5 or earlier pip should | |||
|
27 | automatically give you the latest compatible version of IPython so you do not | |||
|
28 | need to pin to a given version. | |||
|
29 | ||||
|
30 | ||||
|
31 | Prompt Rendering Performance improvements | |||
|
32 | ----------------------------------------- | |||
|
33 | ||||
|
34 | Pull Request :ghpull:`11933` introduced an optimisation in the prompt rendering | |||
|
35 | logic that should decrease the resource usage of IPython when using the | |||
|
36 | _default_ configuration but could potentially introduce a regression of | |||
|
37 | functionalities if you are using a custom prompt. | |||
|
38 | ||||
|
39 | We know assume if you haven't changed the default keybindings that the prompt | |||
|
40 | **will not change** during the duration of your input – which is for example | |||
|
41 | not true when using vi insert mode that switches between `[ins]` and `[nor]` | |||
|
42 | for the current mode. | |||
|
43 | ||||
|
44 | If you are experiencing any issue let us know. | |||
|
45 | ||||
|
46 | Code autoformatting | |||
|
47 | ------------------- | |||
|
48 | ||||
|
49 | The IPython terminal can now auto format your code just before entering a new | |||
|
50 | line or executing a command. To do so use the | |||
|
51 | ``--TerminalInteractiveShell.autoformatter`` option and set it to ``'black'``; | |||
|
52 | if black is installed IPython will use black to format your code when possible. | |||
|
53 | ||||
|
54 | IPython cannot always properly format your code; in particular it will | |||
|
55 | auto formatting with *black* will only work if: | |||
|
56 | ||||
|
57 | - Your code does not contains magics or special python syntax. | |||
|
58 | ||||
|
59 | - There is no code after your cursor. | |||
|
60 | ||||
|
61 | The Black API is also still in motion; so this may not work with all versions of | |||
|
62 | black. | |||
|
63 | ||||
|
64 | It should be possible to register custom reformatter, though the API is till in | |||
|
65 | flux. | |||
|
66 | ||||
|
67 | Arbitrary Mimetypes Handing in Terminal | |||
|
68 | --------------------------------------- | |||
|
69 | ||||
|
70 | When using IPython terminal it is now possible to register function to handle | |||
|
71 | arbitrary mimetypes. While rendering non-text based representation was possible in | |||
|
72 | many jupyter frontend; it was not possible in terminal IPython, as usually | |||
|
73 | terminal are limited to displaying text. As many terminal these days provide | |||
|
74 | escape sequences to display non-text; bringing this loved feature to IPython CLI | |||
|
75 | made a lot of sens. This functionality will not only allow inline images; but | |||
|
76 | allow opening of external program; for example ``mplayer`` to "display" sound | |||
|
77 | files. | |||
|
78 | ||||
|
79 | So far only the hooks necessary for this are in place, but no default mime | |||
|
80 | renderers added; so inline images will only be available via extensions. We will | |||
|
81 | progressively enable these features by default in the next few releases, and | |||
|
82 | contribution is welcomed. | |||
|
83 | ||||
|
84 | We welcome any feedback on the API. See :ref:`shell_mimerenderer` for more | |||
|
85 | informations. | |||
|
86 | ||||
|
87 | This is originally based on work form in :ghpull:`10610` from stephanh42 | |||
|
88 | started over two years ago, and still a lot need to be done. | |||
|
89 | ||||
|
90 | MISC | |||
|
91 | ---- | |||
|
92 | ||||
|
93 | - Completions can define their own ordering :ghpull:`11855` | |||
|
94 | - Enable Plotting in the same cell than the one that import matplotlib | |||
|
95 | :ghpull:`11916` | |||
|
96 | - Allow to store and restore multiple variables at once :ghpull:`11930` | |||
|
97 | ||||
5 | .. _version 790: |
|
98 | .. _version 790: | |
6 |
|
99 | |||
|
100 | IPython 7.9.0 | |||
|
101 | ============= | |||
|
102 | ||||
7 | IPython 7.9 is a small release with a couple of improvement and bug fixes. |
|
103 | IPython 7.9 is a small release with a couple of improvement and bug fixes. | |
8 |
|
104 | |||
9 | - Xterm terminal title should be restored on exit :ghpull:`11910` |
|
105 | - Xterm terminal title should be restored on exit :ghpull:`11910` |
General Comments 0
You need to be logged in to leave comments.
Login now