Open
Conversation
Per w3c#191, letting Bikeshed try and install the latest version is good in general, and results in a much better error message when people try to run this job with a too-old Python.
Member
|
@tabatkins I feel this goes against the dependency-locking plan I mentioned in #141 (comment). I'd like each spec-prod version to have a specific toolchain version (even if major) so people can use it, without any breaking changes. I think warning when using incompatible version would be best, or even better - ensure a compatible python version is installed (#99). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Per #191, letting Bikeshed try and install the latest version is good in general, and results in a much better error message when people try to run this job with a too-old Python.
Closes #191