[SPARK-56135][DOCS] Add option to use venv in PySpark docs#54943
Closed
Yicong-Huang wants to merge 3 commits intoapache:masterfrom
Closed
[SPARK-56135][DOCS] Add option to use venv in PySpark docs#54943Yicong-Huang wants to merge 3 commits intoapache:masterfrom
Yicong-Huang wants to merge 3 commits intoapache:masterfrom
Conversation
|
|
||
| # Python 3.10+ is required | ||
| python3 -m venv .venv | ||
| source .venv/bin/activate # On Windows: .venv\Scripts\activate |
Contributor
There was a problem hiding this comment.
can we not mention windows?
since we even don't have tests run on windows.
this comment suggest pyspark is well supported on windows, but I guess it is not true
zhengruifeng
approved these changes
Mar 23, 2026
Contributor
|
merged to master |
terana
pushed a commit
to terana/spark
that referenced
this pull request
Mar 23, 2026
### What changes were proposed in this pull request? Add a `venv` section in the PySpark documentation as an alternative to Conda for environment management: - `python/docs/source/getting_started/install.rst` - new "Using venv" section alongside "Using Conda" - `python/docs/source/development/contributing.rst` - new "venv" section alongside Conda and pip under Environment Setup ### Why are the changes needed? The PySpark docs currently only mention pip (without isolation) and Conda for environment setup. Python's built-in `venv` module is a lightweight alternative that doesn't require installing Conda. Adding this option gives users more choices for setting up their development environment. ### Does this PR introduce _any_ user-facing change? Documentation only. ### How was this patch tested? N/A (documentation change). ### Was this patch authored or co-authored using generative AI tooling? Yes. Closes apache#54943 from Yicong-Huang/SPARK-56135/add-venv-docs. Authored-by: Yicong Huang <17627829+Yicong-Huang@users.noreply.github.com> Signed-off-by: Ruifeng Zheng <ruifengz@apache.org>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Add a
venvsection in the PySpark documentation as an alternative to Conda for environment management:python/docs/source/getting_started/install.rst- new "Using venv" section alongside "Using Conda"python/docs/source/development/contributing.rst- new "venv" section alongside Conda and pip under Environment SetupWhy are the changes needed?
The PySpark docs currently only mention pip (without isolation) and Conda for environment setup. Python's built-in
venvmodule is a lightweight alternative that doesn't require installing Conda. Adding this option gives users more choices for setting up their development environment.Does this PR introduce any user-facing change?
Documentation only.
How was this patch tested?
N/A (documentation change).
Was this patch authored or co-authored using generative AI tooling?
Yes.