-
-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
Remove xlrd benchmark after xlrd was updated to 2.0.1 on conda-forge #39077
Conversation
Alternatively we could remove this benchmark |
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.
NO, do not pin this. just remove the benchmark
Done |
Have to backport this too. |
great, backporting as well to avoid 1.2.x CI failures |
@jreback greenish based on the changes here. Azure will take a while because of the new master commits |
thanks @phofl |
@meeseeksdev backport 1.2.x |
…dated to 2.0.1 on conda-forge
….0.1 on conda-forge (#39078) Co-authored-by: patrick <61934744+phofl@users.noreply.github.com>
@@ -40,7 +40,7 @@ def time_write_excel(self, engine): | |||
|
|||
class ReadExcel: | |||
|
|||
params = ["xlrd", "openpyxl", "odf"] | |||
params = ["openpyxl", "odf"] |
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.
We could also rather keep this, but with writing an xls file (in addition to the xlsx file) to read with xlrd?
Is pinning here the right thing to do in environment.yml?
cc @jreback