IronLanguages / IronLanguages/ironpython3
Trying to run an unknown module results in Unhandled exception
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 316
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 1
Description
For example, running ipy -m blabla I get the following:
Unhandled exception:
Traceback (most recent call last):
File "C:\Program Files\IronPython 3.4\Lib\runpy.py", line 178, in run_module
File "C:\Program Files\IronPython 3.4\Lib\runpy.py", line 112, in _get_module_details
ImportError: No module named blabla
The expected result would be something like the following (which you get by running ipy -m runpy blabla):
C:\Program Files\IronPython 3.4\ipy.exe: No module named blabla
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with ipy -m blabla and compare it with ipy -m runpy blabla. Start by tracing the ipy -m handling into Lib/runpy.py, especially run_module and _get_module_details. Done means an unknown module reports the concise ipy.exe: No module named blabla message instead of an unhandled traceback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100