##// 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.
MinRK -
r4197:368e365a
Show More
Name Size Modified Last Commit Author
/ IPython / quarantine
tests
InterpreterExec.py Loading ...
__init__.py Loading ...
clearcmd.py Loading ...
envpersist.py Loading ...
ext_rescapture.py Loading ...
ipy_app_completers.py Loading ...
ipy_autoreload.py Loading ...
ipy_completers.py Loading ...
ipy_editors.py Loading ...
ipy_exportdb.py Loading ...
ipy_extutil.py Loading ...
ipy_fsops.py Loading ...
ipy_gnuglobal.py Loading ...
ipy_greedycompleter.py Loading ...
ipy_jot.py Loading ...
ipy_lookfor.py Loading ...
ipy_profile_doctest.py Loading ...
ipy_pydb.py Loading ...
ipy_rehashdir.py Loading ...
ipy_render.py Loading ...
ipy_server.py Loading ...
ipy_signals.py Loading ...
ipy_synchronize_with.py Loading ...
ipy_system_conf.py Loading ...
ipy_which.py Loading ...
ipy_winpdb.py Loading ...
ipy_workdir.py Loading ...
jobctrl.py Loading ...
ledit.py Loading ...
pspersistence.py Loading ...
win32clip.py Loading ...