-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
ENH: added new cache_dates parameter for read_csv func #25990
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
Conversation
Hello @anmyachev! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found: There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻 Comment last updated at 2019-05-07 08:30:55 UTC |
Codecov Report
@@ Coverage Diff @@
## master #25990 +/- ##
===========================================
- Coverage 91.86% 41.9% -49.96%
===========================================
Files 175 175
Lines 52543 52544 +1
===========================================
- Hits 48267 22021 -26246
- Misses 4276 30523 +26247
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #25990 +/- ##
==========================================
- Coverage 91.99% 91.98% -0.01%
==========================================
Files 175 175
Lines 52377 52378 +1
==========================================
- Hits 48182 48180 -2
- Misses 4195 4198 +3
Continue to review full report at Codecov.
|
while we are doing this may as well flip the flag in |
9b0a443
to
2fd52d0
Compare
@jreback I made sure that changing |
0925e56
to
2fd52d0
Compare
Note for reviewers: it seems that this PR have the same errors as master branch |
7ca68a1
to
002c031
Compare
We already have so many datetime parameters at this point, but I'm thinking at some point we should condense them into a @jreback : What do you think? |
Maybe declare a |
@vnlitvin : I'm actually inclined to leave it as |
|
@gfyoung condensation of parameters into |
@anmyachev : Absolutely! Separate PR would be most appropriate. |
@gfyoung ok. Anything left to fix in this PR? |
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.
Over to you @jreback
small comments, otherwise lgtm. Is that an issue for changing this in |
@jreback when changing the flag in |
ed521d6
to
94c0eb5
Compare
@anmyachev this is a troubling comment. #25990 (comment) can you show me an example? |
@jreback is there anything left to fix before this could be merged? |
94c0eb5
to
1c85780
Compare
Does our example (#26097) satisfy you here? I feel that it shouldn't be a blocker for this PR. P.S. I've rebased on |
is there an issue for this? |
@jreback no errors detected for this. |
ee0b37f
to
af757f2
Compare
what does this mean? |
I mean: I not found issue for this. |
If you mean Github issue then no, we didn't file one and we didn't fine any. |
can you merge master. |
af757f2
to
687d0c4
Compare
@jreback Done & green |
thanks @anmyachev |
Are we OK with this slowdown on the parse dates benchmark? http://pandas.pydata.org/speed/pandas/index.html#io.csv.ReadCSVParseDates.time_multiple_date?commits=f65742cd47d6b364a2cbf150869b282c5aa7daf0 |
git diff upstream/master -u -- "*.py" | flake8 --diff
This change allows the user to use caching when parsing dates, which is provided by
to_datetime
function