Fix various PyTorch-related libraries #1263
Closed
Conversation
This file contains 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
Also fix einops and pyngrok.
|
Huh. Apparently I broke |
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.
This is a cleaned-up pile of commits which lets me get most of the way towards building an application using PyTorch. Of note are the
safetensorsandtokenizersfrom HuggingFace, andtiktokenfrom OpenAI; these libraries have upstream issues, as noted in huggingface/tokenizers#1226 and openai/tiktoken#179.This PR hardcodes two
Cargo.lockfiles because upstreams are not willing to do it themselves. If that's not acceptable, then we'll need to figure out another permanent solution. However, I'm currently disinclined to accept any sort of demurral or delay, simply because the Nix way is to patch rather than to wait for upstreams.