##// END OF EJS Templates
remove special handling of ipython_kernel in launcher...
remove special handling of ipython_kernel in launcher - set JPY_PARENT_PID and JPY_INTERRUPT_EVENT env variables for all kernels - no custom kernel args other that console passthrough - use devnull instead of `--no-stdout` (comments claim it shouldn't work, but tests suggest it does - let's keep an eye on this)
Min RK -
r19188:a31d8820
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 ...
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 ...

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.