IronLanguages / IronLanguages/ironpython3
PEP 3131 -- Supporting Non-ASCII Identifiers
Open
Nobody has claimed this yet.
What's New In Python 3.0
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 316
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 1
Description
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 reading PEP 3131 at the linked specification and then inspect the IronPython implementation to identify the parser and identifier-handling entry points. Done means IronPython supports the non-ASCII identifier behavior required by the PEP, with coverage demonstrating the supported cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100