Vyacheslav Rusakov
Vyacheslav Rusakov
I faced that too, and agree that it's not normal, but the following workaround works: ``` release.git.requireBranch.set('master') ```
Yes, configuration cache is not supported yet because there was no alternative to buildFinished listener. But since 8.1 there is a [flowscope api](https://docs.gradle.org/8.1/release-notes.html#new-dataflow-actions-replace-buildfinished-listeners) which could be used instead. I will...
[4.0.0 released](https://github.com/xvik/gradle-use-python-plugin/releases/tag/4.0.0) with configuration cache support
Thank you! I will look it
No, only virtualenv supported. Initially it was required to support both pythons 2 and 3. Now its not as important, but it needs time to implement venv support. Maybe, someday...
Virtualenv should be installed for current user only (`--user`) and should not cause permission errors. But, it seems, it's not always work like that. I'll look to support venv, but...
[4.0.0 released](https://github.com/xvik/gradle-use-python-plugin/releases/tag/4.0.0). Venv now used by default and falls back to virtualenv only if venv not found. There would be no problems with existing projects where environments were already created...