Skip to Content
Browse documentation

Manage Python Applications in UAPP

Review Python application status and change runtime, startup script, public directory, environment and sandbox lifecycle controls in UAPP.

Open Python → Python Applications. This page requires the Python selector feature.

The summary shows application count, enabled count, production/development counts and Ready/Deploying counts. The table lists website, Python version, application type, startup script, public path, environment, deployment status, enabled state and actions. Search and sort to find a website.

Change the runtime

  1. Select Change Python runtime for the website.
  2. Review the website, application and current runtime.
  3. Choose a listed installed Python version.
  4. Choose whether to reinstall packages.
  5. Confirm that you backed up the application and package list, then save.
  6. Wait for deployment work to finish and test the application.

The runtime is checked against the installed version list. A displayed inherited runtime does not add an arbitrary-version or install-new-runtime option.

Reinstalling as part of a version change can remove packages. Skipping reinstall does not guarantee existing packages or compiled extensions work with the new interpreter.

Edit application settings

ControlAccepted input and effect
Startup scriptA filename such as wsgi.py or app.py; starts with a letter or digit, followed by letters, digits, underscores or hyphens, ending in .py. Paths are not accepted. The entry point must exist in the project.
Public directoryA relative directory beneath the website document root, such as public. The website document root itself is not moved.
EnvironmentProduction or Development; rebuilds application service configuration.

Use the pencil or directory/environment action, review the website, enter the value and select Save Changes. Public-directory validation accepts 1–253 characters consisting of word characters, dots, slashes and hyphens; it cannot begin with a dot or slash or end with a dot or slash. Use a simple relative path without traversal components.

Choosing Production is not a substitute for checking your framework's own debug and security configuration.

Enable or disable

Select the sandbox switch and confirm Enable Python Sandbox or Disable Python Sandbox. The switch returns to its current state while confirmation is pending. This rebuilds service configuration; disabling is distinct from deleting the environment.

Reinstall

Select Reinstall Python sandbox, review the warning and acknowledge that you backed up the application and package list. Reinstall uses the current Python version and may remove installed pip packages. Record dependencies first using requirements export.

Delete

Select Delete Python sandbox and explicitly acknowledge removal before confirming. This removes the sandbox runtime, installed packages and service configuration; website files are preserved, but the Python application stops running. The panel resets the application/runtime selection to defaults and removes Python application settings.

Deletion is destructive

Disabling and deleting are different operations. Keep a verified backup and package list before deletion. Preserved website files alone are not a working Python environment.

Busy or failed actions

Deployment in progress disables lifecycle actions and is checked before changes. Wait and refresh. If a marker appears stuck, ask the provider to inspect the task rather than repeatedly reinstalling or deleting.

A failed rebuild may leave newly recorded settings. Review the current state before retrying. Sandbox deletion is blocked in demo mode.