Project

Profile

Help

Issue #5696

closed

dependency pinning makes packaging pulp3 more complicated than necessary

Added by evgeni over 4 years ago. Updated over 4 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
3. High
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 61
Quarter:

Description

pulpcore (today) defines the following requirements:

requirements = [
    'aiohttp',
    'aiofiles',
    'backoff',
    'coreapi~=2.3.3',
    'Django~=2.2.3',  # LTS version, switch only if we have a compelling reason to
    'django-filter~=2.2.0',
    'djangorestframework~=3.10.2',
    'djangorestframework-queryfields~=1.0.0',
    'drf-nested-routers~=0.91.0',
    'drf-yasg~=1.17.0',
    'gunicorn~=19.9.0',
    'psycopg2-binary',
    'PyYAML~=5.1.1',
    'rq~=1.1.0',
    'redis~=3.1.0',
    'setuptools>=41.0.1,<41.7.0',
    'dynaconf>=2.2,<2.3',
    'whitenoise~=4.1.3',
]

I understand that the idea behind this is to ensure that it can only be ever installed with tested dependencies (see https://pulp.plan.io/issues/5196 for the original discussion and decision).

However, this raises the following "issues" when deploying pulpcore via (RPM) packages:

As pulpcore uses pkg_resources.get_distribution at runtime, it will error out when psycopg2-binary or a sufficiently new version of setuptools is not found and Pulp won't work.

While I can easily patch both things during package building, I think this warrants a broader discussion how production grade setups shall be handled.

Also available in: Atom PDF