feat(python/sedonadb-expr): Add Python documentation sources based on SQL documentation#862
Draft
paleolimbot wants to merge 10 commits into
Draft
feat(python/sedonadb-expr): Add Python documentation sources based on SQL documentation#862paleolimbot wants to merge 10 commits into
paleolimbot wants to merge 10 commits into
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
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.
Like #851 but for Python.
This PR generates a package, sedonadb-expr, dynamically at build time based on the SQL documentation. This allows function documentation inline. Because it's a separate package, users that don't need this don't have to pay the cost of loading it (non trivial, given that there are hundreds of functions and thousands of lines of functions + docs).
The pattern here is the "accessor" pattern, which both Pandas and CUDF and ESRI use to get nice type completion (I think this was invented slightly after GeoPandas subclassed the GeoSeries).