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

Version update message for older stacks #476

Closed
lee212 opened this issue Aug 26, 2020 · 5 comments · Fixed by #530
Closed

Version update message for older stacks #476

lee212 opened this issue Aug 26, 2020 · 5 comments · Fixed by #530

Comments

@lee212
Copy link
Contributor

lee212 commented Aug 26, 2020

To encourage using the latest version of RCT, it is useful if a version check is enabled with a message to update.

@iparask
Copy link
Contributor

iparask commented Nov 25, 2020

@lee212, can you provide an example of how you think this might work? I think we may have to go to all tags and add a warning.

@mturilli
Copy link
Contributor

mturilli commented Dec 3, 2020

@lee212 ping

@lee212
Copy link
Contributor Author

lee212 commented Dec 15, 2020

pip warning would be a good example like:

WARNING: You are using pip version 19.2.3, however version 19.3.1 is available.

from https://github.com/pypa/pip/blob/master/src/pip/_internal/self_outdated_check.py

@iparask
Copy link
Contributor

iparask commented Jan 4, 2021

Alright! Does it make sense to include from Jan 2021 release onwards or update all previous releases as well?

@andre-merzky
Copy link
Member

We actually had this implemented with a -v flag on radical-stack which checked pypi for the latest available version. Alas, the pypi interface we used for this became deprecated, and thus a recent PR (radical-cybertools/radical.utils/pull/276) removes that support again until we find a different way to query that information (in a timely and simple fashion).

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

Successfully merging a pull request may close this issue.

4 participants