Python Environment Setup - Revision history

Bacchas at 16:52, 5 January 2026

2026-01-05T16:52:10Z

← Older revision		Revision as of 16:52, 5 January 2026
Line 14:		Line 14:
	* On your PC: Activate the new environment with <code>.venv_pc\Scripts\activate </code> and then run		* On your PC: Activate the new environment with <code>.venv_pc\Scripts\activate </code> and then run
	pip install -r requirements.txt.		pip install -r requirements.txt.
			= Prevent Future Sync Issues =
			*To ensure your Mac environment doesn't accidentally get messed up by your PC (or vice versa), add both environment names to your project's <code>.gitignore</code> file:
			<pre>
			.venv/
			.venv_pc/
			.venv_mac/

			</pre>

Bacchas at 16:50, 5 January 2026

2026-01-05T16:50:34Z

← Older revision		Revision as of 16:50, 5 January 2026
Line 8:		Line 8:
	*Type and select Python: Select Interpreter.		*Type and select Python: Select Interpreter.
	*Choose the one that points to your new folder: <code>('.venv_pc': venv).</code>		*Choose the one that points to your new folder: <code>('.venv_pc': venv).</code>
	If it doesn't appear, select Enter interpreter path... and browse to .venv_pc\Scripts\python.exe.		*If it doesn't appear, select Enter interpreter path... and browse to .venv_pc\Scripts\python.exe.
			= Sync Libraries via requirements.txt =
			*Since you have a new, empty environment, you need to install your project's dependencies:
			* On your Mac (before switching): <code>Run pip freeze > requirements.txt</code> to save a list of your current libraries.
			* On your PC: Activate the new environment with <code>.venv_pc\Scripts\activate </code> and then run
			pip install -r requirements.txt.

Bacchas at 16:21, 5 January 2026

2026-01-05T16:21:28Z

← Older revision		Revision as of 16:21, 5 January 2026
Line 5:		Line 5:
	==Set VS Code to Use the New PC Environment==		==Set VS Code to Use the New PC Environment==
	* You must tell VS Code on your PC to use this specific folder instead of the one from your Mac:		* You must tell VS Code on your PC to use this specific folder instead of the one from your Mac:
	**Press Ctrl + Shift + P to open the Command Palette.		**Press<code> Ctrl + Shift + P</code> to open the Command Palette.
	*Type and select Python: Select Interpreter.		*Type and select Python: Select Interpreter.
	*Choose the one that points to your new folder: <code>('.venv_pc': venv).</code>		*Choose the one that points to your new folder: <code>('.venv_pc': venv).</code>
	If it doesn't appear, select Enter interpreter path... and browse to .venv_pc\Scripts\python.exe.		If it doesn't appear, select Enter interpreter path... and browse to .venv_pc\Scripts\python.exe.

Bacchas at 16:20, 5 January 2026

2026-01-05T16:20:59Z

← Older revision		Revision as of 16:20, 5 January 2026
Line 5:		Line 5:
	==Set VS Code to Use the New PC Environment==		==Set VS Code to Use the New PC Environment==
	* You must tell VS Code on your PC to use this specific folder instead of the one from your Mac:		* You must tell VS Code on your PC to use this specific folder instead of the one from your Mac:
	-Press Ctrl + Shift + P to open the Command Palette.		**Press Ctrl + Shift + P to open the Command Palette.
	*Type and select Python: Select Interpreter.		*Type and select Python: Select Interpreter.
	*Choose the one that points to your new folder: <code>('.venv_pc': venv).</code>		*Choose the one that points to your new folder: <code>('.venv_pc': venv).</code>
	If it doesn't appear, select Enter interpreter path... and browse to .venv_pc\Scripts\python.exe.		If it doesn't appear, select Enter interpreter path... and browse to .venv_pc\Scripts\python.exe.

Bacchas at 16:20, 5 January 2026

2026-01-05T16:20:28Z

← Older revision		Revision as of 16:20, 5 January 2026
Line 3:		Line 3:
	python -m venv .venv_pc		python -m venv .venv_pc
	*This creates a new folder named <code>.venv_pc </code>in your project. Your existing Mac folder <code>(e.g., .venv or .venv_mac) </code>will remain completely untouched.		*This creates a new folder named <code>.venv_pc </code>in your project. Your existing Mac folder <code>(e.g., .venv or .venv_mac) </code>will remain completely untouched.
			==Set VS Code to Use the New PC Environment==
			* You must tell VS Code on your PC to use this specific folder instead of the one from your Mac:
			-Press Ctrl + Shift + P to open the Command Palette.
			*Type and select Python: Select Interpreter.
			*Choose the one that points to your new folder: <code>('.venv_pc': venv).</code>
			If it doesn't appear, select Enter interpreter path... and browse to .venv_pc\Scripts\python.exe.

Bacchas at 16:18, 5 January 2026

2026-01-05T16:18:39Z

← Older revision		Revision as of 16:18, 5 January 2026
Line 2:		Line 2:
	*Instead of the generic .venv, give your Windows environment a name that clearly identifies it. In your project's root terminal, run:		*Instead of the generic .venv, give your Windows environment a name that clearly identifies it. In your project's root terminal, run:
	python -m venv .venv_pc		python -m venv .venv_pc
	*This creates a new folder named <code>.venv_pc </code>in your project. Your existing Mac folder (e.g., .venv or .venv_mac) will remain completely untouched.		*This creates a new folder named <code>.venv_pc </code>in your project. Your existing Mac folder <code>(e.g., .venv or .venv_mac) </code>will remain completely untouched.

Bacchas at 16:18, 5 January 2026

2026-01-05T16:18:04Z

← Older revision		Revision as of 16:18, 5 January 2026
Line 2:		Line 2:
	*Instead of the generic .venv, give your Windows environment a name that clearly identifies it. In your project's root terminal, run:		*Instead of the generic .venv, give your Windows environment a name that clearly identifies it. In your project's root terminal, run:
	python -m venv .venv_pc		python -m venv .venv_pc
	*This creates a new folder named .venv_pc in your project. Your existing Mac folder (e.g., .venv or .venv_mac) will remain completely untouched.		*This creates a new folder named <code>.venv_pc </code>in your project. Your existing Mac folder (e.g., .venv or .venv_mac) will remain completely untouched.

Bacchas at 16:03, 5 January 2026

2026-01-05T16:03:12Z

← Older revision		Revision as of 16:03, 5 January 2026
Line 1:		Line 1:
	==Create the Environment with a Unique Name==		==Create the Environment with a Unique Name==
	*Instead of the generic .venv, give your Windows environment a name that clearly identifies it. In your project's root terminal, run:		*Instead of the generic .venv, give your Windows environment a name that clearly identifies it. In your project's root terminal, run:
	python -m venv .venv_pc		python -m venv .venv_pc
	*This creates a new folder named .venv_pc in your project. Your existing Mac folder (e.g., .venv or .venv_mac) will remain completely untouched.		*This creates a new folder named .venv_pc in your project. Your existing Mac folder (e.g., .venv or .venv_mac) will remain completely untouched.

Bacchas: Created page with "==Create the Environment with a Unique Name== Instead of the generic .venv, give your Windows environment a name that clearly identifies it. In your project's root terminal, run: python -m venv .venv_pc This creates a new folder named .venv_pc in your project. Your existing Mac folder (e.g., .venv or .venv_mac) will remain completely untouched."

2026-01-05T15:47:35Z

Created page with "==Create the Environment with a Unique Name== *Instead of the generic .venv, give your Windows environment a name that clearly identifies it. In your project's root terminal, run: python -m venv .venv_pc *This creates a new folder named .venv_pc in your project. Your existing Mac folder (e.g., .venv or .venv_mac) will remain completely untouched."

New page

==Create the Environment with a Unique Name==
*Instead of the generic .venv, give your Windows environment a name that clearly identifies it. In your project's root terminal, run:
python -m venv .venv_pc
*This creates a new folder named .venv_pc in your project. Your existing Mac folder (e.g., .venv or .venv_mac) will remain completely untouched.