Implement new alternate class table writing method #315
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Should fix #314
It turns out the old ('backup') method for writing class tables just doesn't work with the chunking functionality added in a recent version. To be honest the approach used by that method is overly complicated and much slower than it should have been. I've therefore just written a new non-Pandas method of putting the class data into the class table.
It's worth confirming whether this resolves the issues previously seen by users. It's not obvious what error would cause the Pandas-based method to fail, so it'd be worthwhile to investigate what the actual exception was that caused it to fall back to the alternative writing method in the first place.
I've also moved a bunch of
printstatements into thedebuglogging level so that the user can see them if desired.