-
Notifications
You must be signed in to change notification settings - Fork 870
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conflicting dependencies for a test matrix #9546
Closed
delfick opened this issue
Dec 1, 2024
· 7 comments
· Fixed by #9370 or delfick/extended-mypy-django-plugin#65
Closed
Conflicting dependencies for a test matrix #9546
delfick opened this issue
Dec 1, 2024
· 7 comments
· Fixed by #9370 or delfick/extended-mypy-django-plugin#65
Labels
bug
Something isn't working
Comments
Related #6830 |
I tried to reproduce this, but could not:
|
Ah actually I'm successful if I add the stubs package
|
awesome, thanks :) |
Yup, I can confirm that this will be fixed by #9370. |
🥳 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I want to make it so that I can run the tests for my project against
django==4.2
and separately againstdjango==5.1
, which means if I want that represented in the uv.lock I need to create conflicting dependencies.But I can't figure out how to make this work and I end up with both versions of django in the virtualenv, which means it's always running the tests with django 5.1
Seems to be enough to make
uv lock
work, but then I douv run --group old-django pytest
and it is still using django 5.1My branch where I'm trying to work this out is over at delfick/extended-mypy-django-plugin#65
The way I'm doing it currently is
uv run --with django==4.2.16 pytest
anduv run --with django==5.1.3 pytest
but this means it doesn't end up in the uv.lock.The text was updated successfully, but these errors were encountered: