Python虚拟环境自定义、相对路径设置及无提示符激活等技术咨询

Hey Jordy, let's tackle each of your questions step by step and get that batch script working properly:

1. Setting Up Python Virtual Environment with Relative Paths #

It’s straightforward to create a virtual environment using relative paths—you just need to specify a local directory when creating it:

• Create the virtual environment in your project root (relative to the batch script’s location) using:

  python -m venv ./venv
  

  This will create a venv folder right in your current working directory.
• Activate the environment using the relative path to the activation script:
  • On Windows: .\venv\Scripts\activate.bat
  • On Linux/macOS: source ./venv/bin/activate
• If you already have an existing virtual environment, you don’t need to recreate it—just ensure all references to it in your batch script use relative paths instead of absolute ones.

2. Activate Virtual Environment Without Modifying Cmd Prompt #

There are two easy ways to do this:

Option 1: Modify the Activation Script #

The default activation script adds a (venv) prefix to your prompt. To disable this:

• On Windows, open ./venv/Scripts/activate.bat and comment out or delete this line:

  set "PROMPT=(%VIRTUAL_ENV_NAME%) %PROMPT%"
  

• On Linux/macOS, open ./venv/bin/activate and comment out the lines that modify PS1 (look for lines starting with PS1="().

Option 2: Skip Activation Altogether #

You don’t actually need to "activate" the environment to use it. Instead, directly call the Python interpreter inside the virtual environment:

.\venv\Scripts\python.exe your_script.py

This runs your script using the virtual environment’s Python and packages without altering the prompt at all.

3. Fixing the Failing Batch Script #

The most common issue with batch scripts that fail after activating a virtual environment is forgetting to use the call command when invoking activate.bat. Without call, the activation script takes over the batch process, and any commands after it won’t run.

Here’s a corrected batch script that ties everything together (using relative paths and optional prompt preservation):

@echo off
REM Use "call" to run the activation script without exiting the batch process
call .\venv\Scripts\activate.bat

REM Execute your Python script (uses the virtual environment's Python)
python your_script.py

REM Launch the CEF embedded browser (update the path to match your CEF executable)
start "" ".\cef\cefclient.exe"

REM Optional: Keep the cmd window open to see errors
pause

If you prefer not to modify the prompt, use this version that skips activation entirely:

@echo off
REM Directly use the virtual environment's Python interpreter
.\venv\Scripts\python.exe your_script.py

REM Launch CEF embedded browser
start "" ".\cef\cefclient.exe"

pause

Troubleshooting Tips #

• Double-check all paths (virtual environment, Python script, CEF executable) are relative and correct relative to where you run the batch script.
• Run each command manually in cmd first to confirm they work individually before putting them in the batch script.
• Check for error messages—if the batch window closes too fast, add pause at the end to read them.

内容的提问来源于stack exchange，提问作者Jordy Deweer