feat: propose py person class approach

[ht1204]

Description

• Proposal py person class

[mateacademy-ai-mentor]

Review Summary

Your solution is approved because it correctly implements all required functionality: the Person class, the people class attribute, instance registration in __init__, and the create_person_list function that builds and links wife/husband relationships behave as specified. The example scenario with Ross, Rachel, and Joey would work as intended, including the AttributeError when accessing wife on a person who has no spouse set.

There are a couple of style issues to be aware of for future tasks. First, the create_person_list(people: list) parameter name is confusing because it shadows Person.people; renaming it to something like people_data or person_dicts would better satisfy [CHECKLIST ITEM #1] on descriptive variable names. Second, when you create the instances, you still use person_dict["name"] and person_dict["age"]; switching these to person_dict.get("name") and person_dict.get("age") would align fully with [CHECKLIST ITEM #4] about preferring dict.get() for dictionary access. Overall, your core implementation is solid; just keep refining variable naming and dictionary access style to match the guidelines more closely in future exercises.

---

✨ Please rate this review in the Platform's notification center¹. I will be grateful for your feedback! ✨

Footnotes

1. Rate AI review example ↩

[mateacademy-ai-mentor]

This violates checklist item #1: Use descriptive and correct variable names. Using people here shadows Person.people and makes it less clear that this is a list of dictionaries, not the class-level map of instances.

[mateacademy-ai-mentor]

This violates checklist item #4: When accessing values in a dictionary, it is better to use the dict.get() method instead of explicitly checking for the presence of a key. You are directly indexing the dictionary for "name" and "age"; consider using person_dict.get("name") and person_dict.get("age") to align with the guideline.

[mateacademy-ai-mentor]

This violates checklist item #1: Use descriptive and correct variable names. Using people as a parameter name makes it ambiguous and conflicts conceptually with Person.people (the class attribute). A more descriptive name like people_data would better convey that this is input data.