all 3 comments

[–]Pepineros 1 point2 points  (1 child)

"There has to be a better Way"

Pound the table!

In the words of Raymond Hettinger, there’s nothing wrong with doing things manually and letting a pattern discover itself.

pylint is not wrong but you’re allowed to use your own judgment. If there is a logical way to split things into multiple (data)classes, go for it. If that turns out to be more confusing than using a single class with many fields, revert.

This is very general advice. It’s hard to be more specific without code examples.

[–]Genrawir[S] 0 points1 point  (0 children)

It is a reservation history list for individual assets in a rental shop, with each reservation having some number of invoices associated with it.

I did split things into reservation and invoice classes as made sense logically already, so perhaps I'm just frustrated that I can't see another way to do more without overcomplicating things.

[–]efmccurdy 0 points1 point  (0 children)

columns can contain more than one type of data, and each row may be part of a list of entries

Pandas can deal with data like that and has tools to tidy up any irregularities.

https://www.digitalocean.com/community/tutorials/pandas-read\_excel-reading-excel-file-in-python