-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
STYLE: use option_context almost always #38813
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
Comments
I would like to work on this issue, would it be possible? |
You can use the |
I'm sorry, I accidentally unassigned myself, could you assign me again?, I don't understand what you mean by the take chat command, I don't have the permission to assign myself an issue, do I? |
@ssooffiiaannee You can comment |
take |
take |
take |
take |
Replaces `set_option` except when this function is directly tested. Closes: pandas-dev#38813
we should very rarely be setting / getting options (except to test that functionaily explicity), and instead use
pd.option_context
, e.g. this should be changed:https://github.com/pandas-dev/pandas/pull/31569/files#diff-5974844fa02c9b81f3477198023bd02503bf82da1e3d15df6dfd62cdca48666bR242
pandas/tests/io/formats/test_format.py is a hotbed for incorrect usages like this.
it may be possible to add a pre-commit hook to check for this in all but a small handful of files.
The text was updated successfully, but these errors were encountered: