add sqlite3 check to deeprank_is_available#1625
Merged
Merged
Conversation
rvhonorato
added
enhancement
rvhonorato
enabled auto-merge
July 17, 2026 09:09
amjjbonvin
approved these changes
Jul 17, 2026
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.
What does this PR do and why?
This PR adds an explicit check for deeprank's dependency on the python interpreter to have been compiled with
sqlite3How was this tested?
Running with a python interpreter compiled with
sqlite3and withoutAI assistance
None
Checklist
CHANGELOG.mdupdated for user-facing changesRelated issues
#1624, haddocking/deeprank-gnn-esm#34
Notes for reviewers
This is an edge case, full python installations commonly used by users will have it's python interpreter compiled with
sqlite3- but in thin environments this is not the case.