IronLanguages / IronLanguages/ironpython3
test_support failing interpreter flags tests
Open
Nobody has claimed this yet.
3.6
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 316
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 1
Description
test_args_from_interpreter_flags and test_optim_args_from_interpreter_flags are failing in test_support in 3.6. There are various reasons for the failures:
- -X arguments which are CPython specific
- IronPython has
sys.flags.dont_write_bytecodeset all the time - Repeated args count doesn't match sys.flags (for example
sys.flags.optimizeis 2 when run with-OOOO)
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
Start by examining the test_args_from_interpreter_flags and test_optim_args_from_interpreter_flags tests in test_support, then compare their expectations with IronPython's sys.flags behavior. Done means the tests handle CPython-only -X arguments, IronPython's dont_write_bytecode setting, and repeated optimization arguments correctly under IronPython 3.6.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100