New way to automatically install optional Python dependencies #274

Closed
opened 2023-08-15 21:40:55 +02:00 by blacklight · 0 comments
Owner
  1. The manifest.yaml of an integration should list the system-provided packages for optional Python dependencies when they are available, rather than the pip packages.

  2. Add apk sections to the manifest files.

Reason for 1: as pip is now discouraging installing Python packages in the system folder, and installing the application in a virtual environment isn't always an option, we want to install Python dependencies from the system-provided packages when available.

Reason for 2: Platydock is moving towards using Alpine rather than Ubuntu as a base image, and any official image is likely to be based on Alpine too.

1. The `manifest.yaml` of an integration should list the system-provided packages for optional Python dependencies when they are available, rather than the `pip` packages. 2. Add `apk` sections to the manifest files. Reason for 1: as `pip` is now discouraging installing Python packages in the system folder, and installing the application in a virtual environment isn't always an option, we want to install Python dependencies from the system-provided packages when available. Reason for 2: Platydock is moving towards using Alpine rather than Ubuntu as a base image, and any official image is likely to be based on Alpine too.
blacklight added the
architecture
label 2023-08-15 21:41:12 +02:00
blacklight added this to the core project 2023-08-15 21:41:20 +02:00
blacklight self-assigned this 2023-08-15 21:41:23 +02:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: platypush/platypush#274
No description provided.