Confirm the supported Python version and whether the panel creates the application environment for you. Use the panel-managed environment when the integration requires it.

1. For a self-managed compatible shell, create the environment with the selected Python executable, for example python3 -m venv .venv, in the intended private project location.

2. Use that environment’s Python and pip to install the project requirements. Invoking python -m pip through the selected environment helps avoid installing into a different interpreter.

3. Configure the WSGI, ASGI or worker startup to use the environment’s interpreter or integration path.

4. Keep the dependency specification in the repository and exclude the environment directory from source control. Recreate environments through a controlled install rather than copying them blindly across systems.

5. Test web requests and scheduled commands using the same intended environment, then document the interpreter path for future maintenance.

Where your hosting integration permits a self-managed virtual environment, create it with the approved Python version in a private project path. If the panel already owns the environment, use its supplied path instead of creating a competing one.

python3 -m venv /home/ACCOUNT/apps/catalogue/.venv
/home/ACCOUNT/apps/catalogue/.venv/bin/python -m pip install \
  -r /home/ACCOUNT/apps/catalogue/requirements.txt
/home/ACCOUNT/apps/catalogue/.venv/bin/python -c \
  'import sys; print(sys.executable)'

Replace ACCOUNT and the project location, then configure WSGI, ASGI and scheduled tasks to use that same environment. The printed executable identifies the interpreter without exposing configuration values. Preserve dependency metadata so the environment can be recreated rather than uploading a laptop environment with incompatible paths or binaries.

Expected result: Web and scheduled execution import the reviewed packages from the intended project environment. Updating an unrelated application’s dependencies does not silently change this installation.

Inspect the interpreter and installed package version through private diagnostics. Confirm another application’s dependency update does not change this application’s environment.

A package that imports in SSH but fails in the website often indicates the service uses a different interpreter. Check startup configuration before reinstalling the package globally.

• Creating repeatable Python dependency installations
• Investigating Python packages that need native libraries
• Using environment variables consistently across web and CLI
• Running FastAPI behind a production reverse proxy
• Deploying a Flask application factory on WSGI hosting

• Python Packaging virtual environments
• Python venv