Skip to content

CLN: avoid catching Exception in io.pytables #29810

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

Merged
merged 3 commits into from
Nov 25, 2019

Conversation

jbrockmendel
Copy link
Member

Last one in this file for a bit, scout's honor.

@@ -4242,38 +4243,29 @@ def write_data_chunk(self, rows, indexes, mask, values):
if not np.prod(v.shape):
return

try:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So just nothing hitting these in the test cases right? If so, any insight from git blame as to why this was here in the first place?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pretty much, yah. The blame for these goes to back before we were using github AFAICT, so there arent associated PRs/threads.

@WillAyd WillAyd added the Clean label Nov 23, 2019
@jreback jreback added this to the 1.0 milestone Nov 25, 2019
@jreback jreback added the IO HDF5 read_hdf, HDFStore label Nov 25, 2019
@jreback jreback merged commit d8c6610 into pandas-dev:master Nov 25, 2019
@jreback
Copy link
Contributor

jreback commented Nov 25, 2019

thanks @jbrockmendel

btw you can blame me for most of this code :->

@jbrockmendel jbrockmendel deleted the cln-pytables-exc branch November 25, 2019 23:00
@jbrockmendel
Copy link
Member Author

btw you can blame me for most of this code :->

One that I'm having trouble with you might be able to help: I'd like to make data_columns, index_axes, non_index_axes, etc into properties, but it isn't clear to me what the underlying logic of how they are defined is. maybe it depends on version via create_for_block?

@jreback
Copy link
Contributor

jreback commented Nov 26, 2019

btw you can blame me for most of this code :->

One that I'm having trouble with you might be able to help: I'd like to make data_columns, index_axes, non_index_axes, etc into properties, but it isn't clear to me what the underlying logic of how they are defined is. maybe it depends on version via create_for_block?

data_columns is defined when writing a table (user passed + index columns from the passed frame); or is index columns on the passed frame if not passed

the others are computed from this, meaning

columns in the stored frame + index columns = index_axes = data_columns + non_index_axes

HTH

proost pushed a commit to proost/pandas that referenced this pull request Dec 19, 2019
proost pushed a commit to proost/pandas that referenced this pull request Dec 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Clean IO HDF5 read_hdf, HDFStore
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants