WIP,ENH: Allow configuring the documentation of backends#39
Draft
seberg wants to merge 1 commit intoscientific-python:mainfrom
Draft
WIP,ENH: Allow configuring the documentation of backends#39seberg wants to merge 1 commit intoscientific-python:mainfrom
seberg wants to merge 1 commit intoscientific-python:mainfrom
Conversation
Just starting... I think we should maybe just expose the full entry-point information, since there may be some backend information we would like to have (i.e. a backend description). The function specific info is still convenient of course. I don't want to expose the `Backend` object, although I guess the _namespace_ (which comes directly from the entry-point) should be OK. (Also needs some minimal tests even when it settles.)
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.
Just starting... I think we should maybe just expose the full entry-point information, since there may be some backend information we would like to have (i.e. a backend description). The function specific info is still convenient of course.
I don't want to expose the
Backendobject, although I guess the namespace (which comes directly from the entry-point) should be OK.(Also needs some minimal tests even when it settles.)
xref gh-30.