Preparing better lockFileContents for Pyodide 0.28.1 #144
Conversation
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
WebReflection
force-pushed
the
pyodide-0.28.1
branch
3 times, most recently
from
95add6c to
b8682b2
Compare
WebReflection
force-pushed
the
pyodide-0.28.1
branch
from
eaf8781 to
565332c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As discussed in pyodide/pyodide#5764 (comment) the
lockFileContentsshould simplify stored packages dance so that next Pyodide release we'll be able again to use latest Pyodide with all its greatest features, including fixes for micropip 0.10 which made PyScript fail.I'll keep this MR around because I've witnessed other issues with Pyodide 0.28 in our PyScript tests (everything is fine in here if I patch issues around
lockFileURL) so let's get ready and release ASAP once 0.28.1 lands.