-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
Deprecate using xlrd
engine
#29375
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
Deprecate using xlrd
engine
#29375
Conversation
Thanks! Does this also warn if just using |
Yes - if you call read_excel there are two cases:
|
Hello @cruzzoe! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:
Comment last updated at 2020-01-26 16:36:12 UTC |
@cruzzoe can you merge master? |
Sorry- not sure what you mean. This is a merge request of my branch to master. Are you asking me to update my branch off the tip of master? |
Yep that's it! |
@WillAyd - done |
@cruzzoe unfortunately looks like something went awry with merging master - any idea what steps you might have done? |
I think might have not pulled the latest from upstream before merging. Typically would want to do git fetch upstream
git merge upstream/master
# fix any merge conflicts
git merge --continue
git push origin YOUR_BRANCH |
I originally did: When comparing my branch against upstream/master I see only my new changes. I have reset and redone using merge instead of rebase. |
@cruzzoe can you filter out this warning in the tests? I think OK to apply at the module level - right now this generates a lot of warnings in the CI logs so want to clean that up |
@cruzzoe you still interested in working on this? |
Yes. Sorry for delay. I'll get back to this very shortly!
…On Mon, 23 Dec 2019, 16:06 alimcmaster1, ***@***.***> wrote:
@cruzzoe <https://github.com/cruzzoe> you still interested in working on
this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#29375?email_source=notifications&email_token=ACXR24QSRVJPWAJFKSB33BLQ2DOZ7A5CNFSM4JIH46F2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHRNJJY#issuecomment-568513703>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACXR24WES7JIR2CNL7E7WX3Q2DOZ7ANCNFSM4JIH46FQ>
.
|
Ive implemented what I think is what you are suggesting. Please could you take a look - I believe this will stop warnings in CI now. Also, I looked at CI to confirm my changes are all good, but I see lots of things failing. Are these related to my change? |
Doc failure I think is related: So need to update block where this is throwing the warning |
can you merge master; ping when green. |
all good. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you add a note to the deprecation section as well
Looks like a merge conflict and still some red CI - @cruzzoe can you fix that up? |
@cruzzoe still active? Can you fix up conflicts and get green? |
Yep. Will aim for tonight. Thanks for reminder.
…On Wed, 4 Mar 2020, 01:25 William Ayd, ***@***.***> wrote:
@cruzzoe <https://github.com/cruzzoe> still active? Can you fix up
conflicts and get green?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#29375?email_source=notifications&email_token=ACXR24TCBY5YOOKXHXCVOXDRFWUXRA5CNFSM4JIH46F2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENV3HKI#issuecomment-594260905>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACXR24UTHOEZKGB6XEDP3ITRFWUXRANCNFSM4JIH46FQ>
.
|
@cruzzoe ping on this one again - looks like some merge conflicts to fix |
@cruzzoe can you merge master and get fix up the test? |
Nice PR but looks like this has gone stale. @cruzzoe ping if you’d like to pick backup - still very welcome |
xlrd
engine in favor of openpyxl #28547black pandas
git diff upstream/master -u -- "*.py" | flake8 --diff