refactor(providers): specify NIXPACKS_PYTHON_PACKAGE_MANAGER#1304
refactor(providers): specify NIXPACKS_PYTHON_PACKAGE_MANAGER#1304coffee-cup merged 8 commits intorailwayapp:mainfrom
NIXPACKS_PYTHON_PACKAGE_MANAGER#1304Conversation
lmmx
changed the title
NIXPACKS_PYTHON_PACKAGE_MANAGER
|
Currently, when both requirements.txt and uv.lock exist in a project, the system automatically prioritizes pip (via requirements.txt) because of the fixed priority order in the code. I need to keep requirements.txt in my project for general pip compatibility, but specifically on Railway I'd like to try using uv instead. This PR would allow overriding the default package manager selection through the NIXPACKS_PYTHON_PACKAGE_MANAGER configuration variable, making it possible to choose uv even when requirements.txt is present. |
|
yw, will take a look at the clippy lint failure my bad sorry! |
|
Reviewable once more 🫡 |
|
Just a few more linting failures. You should be able to fix these automatically (or see where they are) with |
lmmx
force-pushed
the
feat-specify-pref-pkg-mgr
branch
from
a1c6264 to
82936aa
Compare
|
I just see one, think I got it! |
|
This pull request is stale because it has been open 10 days with no activity. Remove stale label or comment or this will be closed in 5 days |
…ected PackageManager enum
lmmx
force-pushed
the
feat-specify-pref-pkg-mgr
branch
from
82936aa to
4c00fc1
Compare
Ready to review, not stale! @coffee-cup |
3 participants
This PR refactors the Python rewrite package manager choice logic using an enum to make the decision tree explicitly clear, and thus also to allow a particular branch to be specified in config
Poetry.lock>uv.lockTasks
NIXPACKS_PYTHON_PACKAGE_MANAGERas "poetry", "uv", etc.