Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.9k
Fix default return of Collection.get_{cap,join}style#25810
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
ksunden commentedMay 4, 2023 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
The alternative would be to resolve to the default. As far as I can tell the default is hard codedhere, so not controlled by rcparam. I suppose backendscould override the default? But not convinced that edge case is worth accounting for. |
Yes, this was added in#9523 and, if Either way, we should probably fix the default and documented default to match. |
Test failure is almost certainly the MacOS/Azure/Tk problem we were having. |
If neither are specified at object creation, the default is to be`None`. This broke `get_{cap,join}style` when the enum wrappers werecreated as they assume the internal value is always an enum value.
2f4f08e
to4b99bc6
Compare
Uh oh!
There was an error while loading.Please reload this page.
PR summary
If neither are specified at object creation, the default is to be
None
. This brokeget_{cap,join}style
when the enum wrappers were created as they assume the internal value is always an enum value.This was broken since the initial addition of the enums in#18544, so I'm not sure if it should be backported (minus the typing changes.)
PR checklist