-
-
Notifications
You must be signed in to change notification settings - Fork 503
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
improve setting global options to None #30763
Comments
Author: Markus Wageringel |
Commit: |
New commits:
|
Branch: u/gh-mwageringel/30763 |
comment:2
Wouldn't it be simpler to just use a unique object instead of |
comment:3
Well, yes, but I think that it is common to use Note that, in the example from the description, |
comment:4
Setting new milestone based on a cursory review of ticket status, priority, and last modification date. |
comment:5
Setting a new milestone for this ticket based on a cursory review. |
comment:6
Stalled in |
comment:7
The proposed change is reasonable and simplifies (actually will simplify in the future) the implementation of |
Reviewer: Vincent Delecroix |
Changed branch from u/gh-mwageringel/30763 to |
The
__call__
method of global options is used as getter and setter. This ticket improves this method to properly handle values ofNone
.For example:
(See #30755 for an actual example where
None
is used as a value.)This can be used as a workaround instead:
This ticket makes
config.size(None)
work as a setter. Additionally, a deprecation is added for the keyword-argument syntaxconfig.size(value=None)
, as it is not usually used and this will simplify the implementation a little.Component: misc
Author: Markus Wageringel
Branch/Commit:
4c08256
Reviewer: Vincent Delecroix
Issue created by migration from https://trac.sagemath.org/ticket/30763
The text was updated successfully, but these errors were encountered: