On Aug 6, 2021, at 08:11, Jack DeVries wrote:
> What do you think about an environment variable?
>
> USE_VENV=false make html
>
> Maybe we can use a variable with a more explicit name so people can keep it
> in their environments if they wish?
I think this would compound the problems with
What do you think about an environment variable?
USE_VENV=false make html
Maybe we can use a variable with a more explicit name so people can keep it
in their environments if they wish?
On Fri, Aug 6, 2021 at 7:19 AM Miro Hrončok wrote:
> On 06. 08. 21 12:21, Łukasz Langa wrote:
> >
> >> O
On 06. 08. 21 12:21, Łukasz Langa wrote:
On 4 Aug 2021, at 11:48, Miro Hrončok wrote:
On 04. 08. 21 11:28, Petr Viktorin wrote:
Hi,
A recent change "make html" in the Doc directory create a venv if one wasn't
there before. If you don't want to download sphinx and other dependencies from PyP
> On 4 Aug 2021, at 11:48, Miro Hrončok wrote:
>
> On 04. 08. 21 11:28, Petr Viktorin wrote:
>> Hi,
>> A recent change "make html" in the Doc directory create a venv if one wasn't
>> there before. If you don't want to download sphinx and other dependencies
>> from PyPI, you'll need to adjust y
One of the most important things is that I was **not informed** about how
this affects the release
process and we ended up with a venv packaged in the tarball, unfortunately.
I agree that these changes should be notified to the release manager,
precisely to avoid these situations.
I am trying to
On 04. 08. 21 11:28, Petr Viktorin wrote:
Hi,
A recent change "make html" in the Doc directory create a venv if one wasn't
there before. If you don't want to download sphinx and other dependencies from
PyPI, you'll need to adjust your workflow.
If you already have all the dependencies, the f
