Better documentation around using different python versions for different modules
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 20.6k
- Forks
- 3.3k
- PR merge metrics
- PR metrics pending
Description
Documentation
As far as I can tell from the docs/google searches/looking through github issues, there isn't guidance on the standard or simplest ways to run mypy in a monorepo of sorts where different directories are on different python versions. I was hoping I could use the python_version config option, but it seems like that can only be set on a global level.
I guess one workaround would be replacing calls like mypy . with a series of calls running over specific directories with their specific python versions, but I was wondering if there is a less cumbersome approach.
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
Review the existing documentation and references for the python_version configuration option, then compare them with the monorepo and per-directory use case described in the issue. Done means documenting the standard or simplest supported approach for checking different Python versions across modules, including any necessary command or configuration examples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100