-
-
Notifications
You must be signed in to change notification settings - Fork 18k
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
DEPR: Deprecate as_recarray in read_csv #13373
Conversation
c76f2e6
to
e71aa1e
Compare
check this on Windows I had disabled a number of these tests because of weird crashing |
I don't have Windows 64 though, which is what I think was crashing based on the |
ok, sign up for appveyor, we auto run on this, its a free account, and I think that you can even remote login to debug. In any event I remove the skip for the tests I marked on win64. Also remove the test marked for 2.6 (its a slow one). It passed for me on 3.5 on win-64, but let's see what appveyor says. |
Okay, so if I understand this correctly, remove the |
yep |
Current coverage is 84.24%@@ master #13373 diff @@
==========================================
Files 138 138
Lines 50739 50749 +10
Methods 0 0
Messages 0 0
Branches 0 0
==========================================
+ Hits 42740 42750 +10
Misses 7999 7999
Partials 0 0
|
e71aa1e
to
e7174d4
Compare
@jreback : Removed the |
what about appveyor ? |
@gfyoung can you make the update that @jorisvandenbossche requested here: #13360 (IOW, just edit buffer_lines) |
Broader question: do we actually want to support this feature? (if we want to prune in read_csv keywords, this is maybe a good candidate). Not sure how much used this is. Has this a significant performance/memory benefit over just using |
@jorisvandenbossche good point. yes I think we should deprecate this as well. @gfyoung xref to #10631 (check box 1) for fixing those tests. The test suite works for me on windows 64 (2.7 & 3.5) |
@jreback : Appveyor passed for me as well, so I think we can consider that Windows issue resolved? @jorisvandenbossche : That's a good point. I'll add the deprecation too. That also would help with decoupling |
e7174d4
to
6885bca
Compare
DEPRECATED: this argument will be removed in a future version. Please call | ||
``pd.read_csv(...).to_records()`` instead. | ||
|
||
Return a NumPy recarray instead of a DataFrame after parsing the data. If |
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.
do we test these guarantees?
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.
Of course. The test I added here speaks for itself.
1) Documented and deprecate as_recarray 2) Added as_recarray functionality to Python engine 3) Fixed bug in C engine in which usecols was not being respected in combination with as_recarray
6885bca
to
abaeaef
Compare
@jreback @jorisvandenbossche : deprecated |
ty |
Deprecated back in 0.19.0 xref pandas-devgh-13373.
Deprecated back in 0.19.0 xref gh-13373.
as_recarray
as_recarray
functionality to Python engineusecols
was not being respected in combination withas_recarray