Description

We have opted to use PDM as our package manager for the API and various other Python libraries in the monorepo (with the API migration happening in #4107). We still using Pipenv in many other places and in the interest of consistency between our toolchains, we would like to migrate all these projects over to PDM as well (potentially also reorganise them into the new Python packages directory).

• automations/python/ - Migrate automations to PDM #4625
• documentation/ - @dhruvkb Migrate documentation to PDM #4266
• [-] ingestion_server/ - moved to Convert usages of Pipenv to PDM after the ingestion server removal #4658
• utilities/provider_tallies/ - Migrate utilities/provider_tallies to PDM #4624
• utilities/dead_links/ - Migrate utilities/dead_link to PDM #4623
• utilities/project_planning/- Migrate utilities/project_planning to PDM #4622
• utilities/generate_test_locales/ - Migrate utilities/generate_test_locales to PDM #4626

More

We also have many references to Pipenv, specifically Pipfile and Pipfile.lock scattered across the codebase. Once these projects are no longer using Pipenv, these references will also need to be updated.

• documentation/general/general_setup.md
• documentation/automations/guides/quickstart.md - Migrate automations to PDM #4625
• [-] documentation/meta/maintenance/elasticsearch_cluster.md
• [-] ingestion_server/Dockerfile - moved to Convert usages of Pipenv to PDM after the ingestion server removal #4658
• [-] ingestion_server/.dockerignore - moved to Convert usages of Pipenv to PDM after the ingestion server removal #4658
• [-] ingestion_server/justfile - moved to Convert usages of Pipenv to PDM after the ingestion server removal #4658
• [-] .pre-commit-config.yaml - moved to Convert usages of Pipenv to PDM after the ingestion server removal #4658
• [-] .github/actions/setup-env/action.yml - moved to Convert usages of Pipenv to PDM after the ingestion server removal #4658

Additional context

The goal is to make a number of small atomic PRs, that migrate only one project and its references per PR, so that they can be quickly verified to work and merged. Please comment below which tasks from above you will be working before starting work on them.