Draft
Conversation
This allows using pywebnn with Python 3.14 without needing to set any environment variables that allow usage with unknown Python versions.
5 tasks
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
1 participant
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.
TensorRT is now on pip https://pypi.org/project/tensorrt-rtx/
We can use it to get the libraries and use the is-installed in our backend decision. Still not perfect since we don't check whether we have a NV GPU that is Turing or newer (and preferably Ampere or newer) with working driver. I have the feeling the backend decision could be done in RustNN itself (after the user selected all allowed backends)
Look at second commit. PR is on top of #9