feat: add project template with uv package manager
#1057
Conversation
| && echo "Installing dependencies:" \ | ||
| # Check if playwright is already installed | ||
| && PLAYWRIGHT_INSTALLED=$(pip freeze | grep -q playwright && echo "true" || echo "false") \ | ||
| && if [ "$PLAYWRIGHT_INSTALLED" = "true" ]; then \ |
There was a problem hiding this comment.
Not sure I follow, so I will think aloud:
This is here because we might already have some version of playwright installed in the base image in location "/usr/local". When we do, we exclude it from uv sync -> which btw syncs to where the python installation lives (so no isolated environment, but isolation is the image - so who cares).
If there is specific playwright version requirement(probably just theoretical use case) - we will ignore it and take whatever version already exists in the base image.
Is my understanding correct?
There was a problem hiding this comment.
That's right, playwright may already be installed in the standard FROM apify/actor-python-playwright image.
This is similar to the logic used in poetry, but keeping the features that uv provides
3 participants
Description
uvpackage managerIssues
uvoption to package manager selection in project bootstrapping #1053