##// END OF EJS Templates
Remove set-next input when triggering help....
Remove set-next input when triggering help. This was a long standing feature from when the main way to edit code was readline. Now that we have proper history and editing frontend, including prompt toolkit this is not necessary, especially since it creates issue like in JupyterLab. Should close #13602
Matthias Bussonnier -
r27619:32c393b6
Show More
Name Size Modified Last Commit Author
/ docs / source / whatsnew
pr
development.rst Loading ...
github-stats-0.11.rst Loading ...
github-stats-0.12.rst Loading ...
github-stats-0.13.rst Loading ...
github-stats-1.0.rst Loading ...
github-stats-2.0.rst Loading ...
github-stats-3.rst Loading ...
github-stats-4.rst Loading ...
github-stats-5.rst Loading ...
github-stats-6.rst Loading ...
github-stats-7.rst Loading ...
github-stats-8.rst Loading ...
index.rst Loading ...
version0.10.rst Loading ...
version0.11.rst Loading ...
version0.12.rst Loading ...
version0.13.rst Loading ...
version0.8.rst Loading ...
version0.9.rst Loading ...
version1.0.rst Loading ...
version2.0.rst Loading ...
version3.rst Loading ...
version3_widget_migration.rst Loading ...
version4.rst Loading ...
version5.rst Loading ...
version6.rst Loading ...
version7.rst Loading ...
version8.rst Loading ...

Documenting What's New

When making a new pull request that either adds a new feature, or makes a
backwards-incompatible change to IPython, please add a new .rst file in this
directory documenting this change as a part of your Pull Request.

This will allow multiple Pull Requests to do the same without conflicting with
one another. Periodically, IPython developers with commit rights will run a
script and populate development.rst
with the contents of this directory, and clean it up.

Files which describe new features can have any name, such as
antigravity-feature.rst, whereas backwards incompatible changes must have
have a filename starting with incompat-, such as
incompat-switching-to-perl.rst. Our "What's new" files always have two
sections, and this prefix scheme will make sure that the backwards incompatible
changes get routed to their proper section.

To merge these files into :file:whatsnew/development.rst, run the script :file:tools/update_whatsnew.py.