How do use Pygradle tasks with a custom virtualenv name.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 603
- Forks
- 142
- PR merge metrics
- No merged PRs in 30d
Description
Pygradle comes with pre-made tasks which is very handy for getting up and running after you figure out the gotchas. One gripe though is they all seem to depend on a virtualenv called `venv`. If you disable to createVirtualEnv tasks or use something else for virtualenv creation all the other premade tasks fail as they depend on an env called `venv`
Is there a way to change this for all tasks ?
Contributor guide
No contributing guide indexed for this repository
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 by reading the Pygradle pre-made task definitions and the virtualenv configuration described in the issue. Determine how those tasks assume the name `venv`; done means they work when virtual-environment creation is disabled or a custom virtualenv name is configured.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100