##// END OF EJS Templates
disallow no-prefix `ipython foo=bar` argument style....
disallow no-prefix `ipython foo=bar` argument style. This style is in rc1, but will be removed in rc2. Since they don't match any flag pattern, rc1-style arguments will be interpreted by IPython as files to be run. So `ipython gui=foo -i` will exec gui=foo, and pass '-i' to gui=foo. Presumably this file won't exist, so there will be an error: Error in executing file in user namespace: gui=foo Assignments *must* have two leading '-', as in: ipython --foo=bar all flags (non-assignments) can be specified with one or two leading '-', as in: ipython -i --pylab -pdb --pprint script.py or ipython --i -pylab --pdb -pprint script.py but help only reports two-leading, as single-leading options will likely be removed on moving to argparse, where they will be replaced by single-letter aliases. The common remaining invalid option will be: ipython -foo=bar and a suggestion for 'did you mean --foo=bar'? will be presented in these cases.

File last commit:

r1261:a818e11a merge
r4197:368e365a
Show More
api_changes.txt
34 lines | 860 B | text/plain | TextLexer
=============
API Changes
=============
.. contents::
..
1 Purpose
2 Version 0.8.2
Purpose
=======
This file documents backwards-incompatible changes to the IPython API,
including user-visible changes of commands, magics, etc.
It should be filled in reverse chronological order, with one section for each
release (which means changes since the previous release).
Version 0.8.2
=============
Changes made since version 0.8.1 was released:
* %pushd/%popd behave differently; now "pushd /foo" pushes CURRENT directory
and jumps to /foo. The current behaviour is closer to the documented
behaviour, and should not trip anyone.
Version 0.8.3
=============
* pydb is now disabled by default (due to %run -d problems). You can enable
it by passing -pydb command line argument to IPython. Note that setting
it in config file won't work.