##// 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:

r1251:99658885
r4197:368e365a
Show More
ipython_here_shell_extension.reg
5 lines | 194 B | text/x-windows-registry | RegeditLexer
/ docs / examples / core / ipython_here_shell_extension.reg
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\Directory\shell\IPython here]
[HKEY_CLASSES_ROOT\Directory\shell\IPython here\Command]
@="cmd.exe /C ipython.py -p sh -i -c \"%cd %1\""