Skip to content

Conversation

@nmm0
Copy link
Contributor

@nmm0 nmm0 commented Apr 24, 2025

No description provided.

We recommend using a virtual environment, e.g. if your system python is >= 3.12:

```sh
python -m venv venv
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it recommended practice to call it "venv" as a default name?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

https://docs.python.org/3/library/venv.html

It says

Contained in a directory, conventionally named .venv or venv in the project directory, or under a container directory for lots of virtual environments, such as ~/.virtualenvs.

So I just picked one but you can name it anything you like

```sh
python -m venv venv
source venv/bin/activate
pip install -r build_requirements.txt
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you remember why we didn't just call it requirements.txt?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Honestly I don't remember, I think some of the NGA folks did that on the initial switch to sphinx. I think requirements.txt is more conventional but I'm not sure

@nmm0
Copy link
Contributor Author

nmm0 commented Apr 24, 2025

Replaced by #672

@nmm0 nmm0 closed this Apr 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants