-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
DOC: Fix flake8 issue in whatsnew files #24177
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
Thanks for creating the issue @saurav2608 Did you check if the changes required are small to have a single PR for all files? I'm guessing if it'd make sense to create an issue to fix all the If you want to take a look yourself, may be fix some cases, see what's reasonable to do (in terms of having issues that are not too big), and create the issues, that would be really great. Otherwise I'll take a look myself. |
@datapythonista : |
Sounds good. I'd start by the newest whatsnew files, and if you see there are too many F405 errors for one PR, just open one half way and continue in another. Huge PRs make reviews very inefficient. |
I have created a PR for errors in recent whatsnew ( v20.0 and above). I am creating issues for the flake-8 error. One for each whatsnew. |
I changed the formats in the table to be the same as the issue for the other For the Thanks a lot for taking care of this. |
@saurav2608 Can you update the table: status of whatsnew files for my PR? This PR is related to |
updated |
@jreback - this issue should remain open. This is a master issue with reference to all the issues in whatsnew. |
@saurav2608 see my comment don’t put ‘closes’ in the PR, instead use xref |
@jreback I see what you mean. This issue changed over time. Going forward it will be streamlined. |
@datapythonista : can you have a quick look at the issue I pointed to in the PR #24236. I am cleaning up the above table need clarifications. |
@saurav2608 I couldn't find the issue, can you send me the link to the exact comment, or tag me on it? |
@datapythonista : I tagged you on that. I am not able to get the link to the exact comment (it is a review ). I have added a new comment tagging you. Line 1036. |
I can't find anything in #24236 and didn't received any notification, no idea what's going on, but no idea what's the issue, sorry. |
@datapythonista : I am replicating the comment here. The issue is near line 1030. I know this is closed and merged. But I noticed an exception while building docs on my local. And traced it back to here. This 2 space indentation is probably wrong. In my local build, I am getting an error
The indentation puts this line of code inside |
ok, I see, can you open a PR to remove the indentation please? |
these are left (aside from open PR to fix 0.15.x)
|
There are no issues created for one and two above. I can create those and if reasonable effort finish them off. |
@jreback / @datapythonista - this issue is now closed. All what whatsnew files are off the exception list. |
thanks a lot for this @saurav2608 |
In some of the whatsnew files we are using implicit imports. For example in "whatsnew/v0.11.0.rst"
we import pandas
from pandas import *
implicitly. We instantiate using the implicitly imported classDataFrame
later in the code.df1 = DataFrame(randn(8, 1), columns = ['A'], dtype = 'float32')
df1
The preferred approach is to use explicit import as
import pandas as pd
and replace the call toDataFrame
withpd.DateFrame
.Note:
import pandas as pd
is part of the header, so it is imported by default. In that case just replacingDataFrame
withpd.DateFrame
and removingfrom pandas import *
should be enough.pd.*
. However, the import statement offrom pandas import *
is included by default. In such case, just remove the import statement.cc: @datapythonista
Status of whatsnew files
The text was updated successfully, but these errors were encountered: