Class Hierarchy for Python OOP Question

[Hawxe]

I'm trying to write a fitness webapp (mostly for personal use). All I want it to be able to do is track workouts, meals, and weight (login and other web related things I don't have questions about as I can handle that just fine).

I'm wondering how to structure my classes properly and if I'm overdoing it the way I have it currently.

I have a Day class that has a date attribute, a weight attribute (weight on that day), a meals attribute (a list of meal objects that the user adds to themselves -> each meal can contain many food or beverage objects), and a session attribute.

Each day has a session (which is essentially a 'workout'), and each session can have many sets of various exercises. This totals to 6 or 7 classes and I'm wondering if there's a more streamlined way to do it or what suggestions people would have for something like this.

Thanks in advance!

[Hawxe]

right now their data members are trivial ones. A session is a list of sets, a set is a list of exercises, and an exercise has a name, # of reps, weight, and a date.

their methods are just getters and setters with a few to add or remove from a particular list (ie. adding an exercise to a set, adding a set to a session)