##// END OF EJS Templates
Fix jedi 0.11 – be optimistic....
Fix jedi 0.11 – be optimistic. Instead of not trying Jedi completion if Jedi parsing of wether we are in a string fails assume that we should alway try jedi, and do not only if jedi manage to prove we are currently in a string. This should give some false positive (like triggering jedi in some unfinished strings), but no false negative – like for example with Jedi 0.11 which is just out. In the end we should do a proper fix; but I'd like to get that soon as otherwise Jedi is quasi deactivated when version 0.11 is installed (released a few days ago).
Matthias Bussonnier -
r23948:1284ba39
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 ...
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 ...

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.