Skip to Content
Browse documentation

Manage Python Packages and Requirements in UAPP

Install, update or remove sandbox pip packages and download requirements.txt in UAPP, with supported input syntax and confirmation steps.

From Python → Python Packages, select a website's package manager. You can also use Manage Python packages in Python Applications.

The selected website must belong to your account and the Python Apps feature must be enabled.

Install packages

  1. Enter one or more packages in Python Packages.
  2. Separate entries with newlines or commas.
  3. Select Install Packages.
  4. Review the website, package count and package names in the confirmation.
  5. Confirm, wait for processing and refresh the installed list.

Examples accepted by the panel's input validator:

Django==5.2
pymongo
requests>=2.32

Each entry supports a package name and an optional single comparison/version expression. Accepted comparisons are ==, >=, <=, ~=, !=, > and <. Names start with a letter or digit and may contain letters, digits, underscores, dots, plus signs and hyphens.

The form is a restricted package-entry field, even though its help mentions requirements.txt syntax. It is not a complete requirements-file parser: do not paste comments, pip options, URLs, editable installs, extras, environment markers or multi-clause constraints such as requests>=2,<3. Submit one supported expression per package. Entries are trimmed, deduplicated and sorted before task submission.

Inspect and update

The installed table shows package names, versions and actions. Search or sort to locate a dependency.

Use the individual update action, or select packages and choose Update Selected. Review the selected names and confirm. The update handler submits package installation work; inspect the resulting versions rather than treating the initial message as a completed upgrade.

Remove packages

Use an individual remove action or Remove Selected. Review the website and package list, acknowledge that removal may stop the application, then confirm.

Removing a dependency can stop the application

Check direct and indirect application requirements before removal. The panel confirmation is not a dependency compatibility analysis. Keep the old package list and a recovery plan.

Package removal is explicitly blocked in demo mode. Install and update do not have the same explicit check in the reviewed handlers.

Download requirements.txt

Select Download requirements.txt. The download is named for the website and contains installed package names, usually as name==version, sorted by name. An entry without an available version is exported as a name alone.

This exports the installed environment, including packages your application may not directly declare. It does not export application files, databases, interpreter binaries, system libraries or configuration. Review it before using it to recreate an environment elsewhere.

In-progress or failed work

Package actions check whether Python deployment is already in progress. Wait for it to finish. A message that an operation started does not guarantee package installation completed successfully.

If versions do not change or imports fail, check the application's Python compatibility and ask the provider to inspect installation output. Do not repeatedly submit the same package change while work may still be running.