Skip to content
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

Unable to install v0.16.4 via pip #53

Closed
sidmitra opened this issue Dec 21, 2020 · 7 comments
Closed

Unable to install v0.16.4 via pip #53

sidmitra opened this issue Dec 21, 2020 · 7 comments
Assignees
Labels

Comments

@sidmitra
Copy link

sidmitra commented Dec 21, 2020

Describe the bug
PYPI describes the latest version as 0.16.4 but unable to install it.

To Reproduce

pip install django-scim2==0.16.4

Expected behavior

  • 0.16.4 installs correctly

Stacktrace

Collecting django-scim2==0.16.4
  Using cached django_scim2-0.16.3-py3-none-any.whl
ERROR: Requested django-scim2==0.16.4 from file:///Users/myuser/Library/Caches/pip/wheels/93/3f/bf/0a26b7ee52fda2c188c8d752d3d7611a6ff375c84b9d0deb01/django_scim2-0.16.3-py3-none-any.whl (from -r requirements.txt (line 64)) has different version in metadata: '0.16.3'
@sidmitra
Copy link
Author

It would seem there's no tagged release for 0.16.4? The last tag i see is 0.16.3 as of today.

@sidmitra sidmitra changed the title Unable to install v0.16.4 via requirements.txt Unable to install v0.16.4 via pip Dec 21, 2020
@logston
Copy link
Collaborator

logston commented Dec 23, 2020

Thanks for finding this issue! Fixed! You'll need to use 0.16.5 though.

@logston logston closed this as completed Dec 23, 2020
@sidmitra
Copy link
Author

sidmitra commented Jan 19, 2021

@logston I think there is still an issue. pyproject.toml on master still mentions the version as 0.16.3 so it's confusing pip/poetry sometimes.

Or rather when i install it through poetry, it seems to work. But pip complains with the following.

ERROR: After October 2020 you may experience errors when installing or updating packages. This is because pip will change the way that it resolves dependency conflicts.

We recommend you use --use-feature=2020-resolver to test your packages with the new resolver before it becomes the default.

myproject 0.1.0 requires django-scim2==0.16.5, but you'll have django-scim2 0.16.3 which is incompatible.

This could be a local issue on my end, but regardless my assumption is that the pyproject.toml version should match what is in setup.py etc. Perhaps it just got missed accidentally.

@logston
Copy link
Collaborator

logston commented Jan 23, 2021

Shucks. Can you try 0.16.6 and see if the issue is fixed?

@sidmitra
Copy link
Author

@logston Thanks for the update. I will take a look later today/tomorrow and leave a comment here.

I've gotten decent mileage out of bumpversion to update version string together in different files. It's worth a look if you're not already using it.

@logston
Copy link
Collaborator

logston commented Jan 23, 2021

Thanks for mentioning the issue! And I'll take a look at bumpversion

@sidmitra
Copy link
Author

@logston Seems to work now. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants