Add option for virtualenv.
Open
- Dominant language
- JavaScript
- Stars
- 6
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Add configuration for selecting a virtualenv to run the task in (as opposed to just assuming they'll already be in the virtualenv.)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the Grunt task configuration and the code that invokes flake8, then inspect how it currently relies on the caller's active virtualenv. Done means the task accepts a virtualenv selection and runs flake8 within it; no test file or entry point is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100