-
Notifications
You must be signed in to change notification settings - Fork 31
Open
Labels
enhancementNew feature or request.New feature or request.t-toolingIssues with this label are in the ownership of the tooling team.Issues with this label are in the ownership of the tooling team.
Description
Context
Crawlee for Python already supports choosing from multiple package managers (pip, uv, poetry) when scaffolding a new project. The Apify Actor templates should offer the same flexibility (for both Python and JS/TS) to provide a better DX.
Goal
When creating a new Python Actor based on the Actor template, users should be able to choose their preferred package manager (pip, uv, poetry, pdm, hatch - decide which makes sense).
Each option should generate the appropriate lock file and configure the Dockerfile/build accordingly.
Potential roadblocks / coordination
- Apify CLI — Add support for package manager choice.
- Apify Console — The Console's "Create Actor" flow and any template selection UI need to support the package manager choice as well.
Reference
- Parent epic: https://github.com/apify/apify-core/issues/25871
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementNew feature or request.New feature or request.t-toolingIssues with this label are in the ownership of the tooling team.Issues with this label are in the ownership of the tooling team.