-
-
Notifications
You must be signed in to change notification settings - Fork 481
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sage_getargspec mishandles keyword-only arguments #31309
Comments
This comment has been minimized.
This comment has been minimized.
comment:2
The implementation of |
comment:3
If we can't get rid of |
comment:4
Sage development has entered the release candidate phase for 9.3. Setting a new milestone for this ticket based on a cursory review of ticket status, priority, and last modification date. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Commit: |
comment:9
Without #26254, Instead we should create a function New commits:
|
This comment has been minimized.
This comment has been minimized.
We rebase `sage_autodoc` to Sphinx 5.3.0. This is a step toward eventual removal of sage_autodoc in sagemath#30893, a customization of Sphinx autodoc extension for Sage objects. Other related tickets are sagemath#27578. sagemath#30884, sagemath#31309, in this regard. URL: https://trac.sagemath.org/34730 Reported by: klee Ticket author(s): Kwankyu Lee Reviewer(s): Tobias Diez
sage_getargspec
seems broken for functions with keyword-only arguments.In #31307, the sphinx documentation for
is generated as
What's happening here is:
In this ticket, we deprecate this function and replace all uses by a new function
signature
that is compatible with inspect.signature:CC: @yuan-zhou @tobiasdiez @kwankyu @fchapoton @tscrim
Component: documentation
Branch/Commit: u/mkoeppe/sage_getargspec_mishandles_keyword_only_arguments @
f6a0eb9
Issue created by migration from https://trac.sagemath.org/ticket/31309
The text was updated successfully, but these errors were encountered: