Support for non-ASCII strings (a.k.a. internationalization)
Open
Nobody has claimed this yet.
API
bug
enhancement
priority-low
- Dominant language
- Python
- Stars
- 128
- Forks
- 110
- Avg merge
- 5d 14h
- Merged PRs (30d)
- 10
Description
For the most part, our APIs only use ASCII strings. There are possible exceptions. For example, if a device name contains international characters (as configured in MAX), customer should be able to create a Session to it.
This should work on all supported Python versions.
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
No file, test, or entry point is named. Start by locating the API paths that accept device names and the tests covering Session creation, then check string handling across the supported Python versions. Done means a Session can target a device name containing international characters and the relevant tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, internationalization
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100