Extension modules - update MSVC for standalone module
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.1k
- Forks
- 1k
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 12
Description
The page https://devguide.python.org/developer-workflow/extension-modules/#updating-msvc-project-files has recently been updated with fantastic content.
However, it currently only shows how to add a built-in module for Windows, and not a separate extension module.
We should add a second section that adds a new .vcxproj for the new extension module (or more likely copies a recommended existing one), along with the other changes necessary to ensure the new module is correctly built and distributed.
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 developer workflow page's “Updating MSVC project files” section linked in the issue. Document the additional steps for creating or copying a .vcxproj for a standalone extension module, including the build and distribution changes; done when the page covers both built-in and separate extension modules.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100