IronLanguages / IronLanguages/ironpython3
Create separate posix module for Unix based platforms
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 316
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 1
Description
We currently just remove builtins['nt'] and assign builtins['posix'] to be the nt module. There is some overlap in functionality, but there are some things that would be much easier to implement in separate modules. Another option would be to use a #if check on Mono builds and have to separate releases, one for Windows and one for Unix based systems. This also doesn't even bring in the concept of running on OSX, which may have some additional changes.
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
The issue does not name files, tests, or entry points. Start by locating the current builtins['nt'] removal and builtins['posix'] assignment, then clarify the Unix, Windows, and OSX module boundaries and release approach. Done means platform-specific behavior is separated without relying on the current NT-module alias.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python
- Domain
- operating-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100