Should we drop support for Cygwin?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 10.7k
- Forks
- 1.9k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 5
Description
Windows Subsystem for Linux has taken lots of mindshare from Cygwin, slowing its development to the point where its default Python is now v3.9, which is end-of-life. Given that our README.md suggests a supported version of Python, we will soon stop supporting and testing Python 3.9.
Will Cygwin upgrade to a supported version of Python? If not, what would be the impact of us dropping support for Cygwin?
- Mentions of
Cygwinin code, issues, pull requests: https://github.com/search?q=repo%3Anodejs%2Fnode-gyp+cygwin
Perhaps this solves things?
https://cygwin.com/packages/summary/python312.html vs.
https://cygwin.com/packages/summary/python3.html (v3.9).
Node-gyp usage on Cygwin is blocked by:
- cygwin/cygwin-install-action#55
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 README.md and the linked search for Cygwin mentions in code, issues, and pull requests. Review the Cygwin installation blocker at cygwin/cygwin-install-action#55 and compare the supported Python versions referenced in the issue. Done means documenting the impact of dropping Cygwin support and reaching a project decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100