| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
(#102697)
gh-102354: change python3 to python in docs examples (GH-102696)
(cherry picked from commit 80abd62647b2a36947a11a6a8e395061be6f0c61)
Co-authored-by: Paul Watson <paul.hermeneutic@gmail.com>
|
| |
|
|
|
| |
(cherry picked from commit 45d014e03ba7ba4c9c912120ec36b2aca02061f4)
Co-authored-by: François Magimel <magimel.francois@gmail.com>
|
| | |
|
| |
|
|
|
|
|
| |
@vsajip Sorry for the trouble—made a [fairly significant] git error in the previous PR.
Have edited the patch as you had said in #28959.
Automerge-Triggered-By: GH:vsajip
|
| | |
|
| |
|
|
|
|
|
|
|
| |
In the [official tutorial on virtual environment](https://docs.python.org/3/tutorial/venv.html#creating-virtual-environments)
> This will create the tutorial-env directory if it doesn’t exist, and also create directories inside it containing a copy of the Python interpreter, **the standard library**, and various supporting files.
According to the actual behavior of `venv` and [PEP 405](https://www.python.org/dev/peps/pep-0405/#id15)'s description about virtual environment, no standard library file is included in the virtual environment's directory.
Automerge-Triggered-By: GH:vsajip
|
| |
|
| |
Add a versionadded for PS Core and note that `.venv` is a common virtual environment name.
|
| |
|
| |
This is to help prevent people from accidentally installing into the wrong Python interpreter if they are not aware of which Python interpreter `pip` points to.
|
| |
|
|
| |
(GH-6814)
|
| |
|
|
|
|
|
|
|
| |
As part of the update, the documentation was updated to normalize
around the term "virtual environment" instead of relying too heavily
on "venv" for the same meaning and leading to inconsistent usage of
either.
Thanks to Steve Piercy for the patch.
|
| | |
|
| | |
|
| |
|
