New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
irunner command line options defer to file extensions #594
Comments
forget that I am just to stupid to read the help message: |
It seems that the file extension takes priority over the options passed, so a .py file is run in PythonRunner. It makes sense that the command line flags should have priority over file extensions, and it should be easy to change. For --interact, make sure you follow the instructions in the usage message - you need an extra |
Reopened because I think the command line options should take priority over file extensions, but it's lower priority. |
Merged in at 10c2367. |
Running
irunner --ipython script.py
currently sees the .py extension, and chooses the Python runner. Command line options should probably override file extensions.Original bug report:
when running irunner from git head with --interact or -i:
$ irunner --interact /tmp/test.py
Usage:
irunner [options] file_to_run
...
irunner: error: no such option: --interact
also the --ipython option does not seem to work, it has regular python prompts and not the ipython prompts:
$ irunner /tmp/test.py
The text was updated successfully, but these errors were encountered: