IronLanguages / IronLanguages/ironpython3
_string.formatter_parser differences with CPython
Open
Nobody has claimed this yet.
CPython compatibility
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 316
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 1
Description
Failures with IronPython but not CPython
list(_string.formatter_parser("{0!}}"))
Failures with CPython but not IronPython
list(_string.formatter_parser('{0.{:{.}.}}'))
list(_string.formatter_parser('{0.{:.}.}'))
list(_string.formatter_parser('{0.{!.:{.}.}}'))
list(_string.formatter_parser('{0.{!!:{.}.}}'))
list(_string.formatter_parser('{0[}'))
list(_string.formatter_parser('{0.[}'))
The failure messages also vary quite a bit.
Issues are from IronPython.test_strformat.
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 with the cases listed in the issue and the IronPython.test_strformat tests, running each against IronPython and CPython to record parser results and error messages. Trace the formatter_parser implementation and its tests; done means the listed discrepancies and failure messages match CPython.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python
- Domain
- compilers, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100