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

Updating non-MSL packages can install the wrong version #7

Closed
jborbely opened this issue Jul 28, 2021 · 1 comment
Closed

Updating non-MSL packages can install the wrong version #7

jborbely opened this issue Jul 28, 2021 · 1 comment

Comments

@jborbely
Copy link
Contributor

msl-io depends on xlrd<2.0; however, executing

msl update --non-msl

could install the wrong version of xlrd, for example,

The following non-MSL packages will be UPDATED:

    xlrd             1.2.0  --> 2.0.1,<2.0  [PyPI]

msl-package-manager will discover inconsistent dependencies when a package is updated (via pip's logging of error messages to the console) but this dependency resolver of pip was officially added in version 20.3. Therefore, as long as pip v20.3+ is installed the appropriate version of xlrd would get installed, but the latest version would be initially installed. For older versions of pip that do not write error messages for inconsistent dependencies to the console, the wrong version of xlrd would remain installed.

jborbely added a commit that referenced this issue Jul 28, 2021
@jborbely
Copy link
Contributor Author

fixed in 8d4ab5b

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

No branches or pull requests

1 participant