Skip to content

Solution#3464

Open
difuz1x wants to merge 5 commits intomate-academy:masterfrom
difuz1x:master
Open

Solution#3464
difuz1x wants to merge 5 commits intomate-academy:masterfrom
difuz1x:master

Conversation

@difuz1x
Copy link
Copy Markdown

@difuz1x difuz1x commented Apr 18, 2026

No description provided.

Copy link
Copy Markdown

@mateacademy-ai-mentor mateacademy-ai-mentor left a comment

Choose a reason for hiding this comment

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

Review Summary

I am requesting changes because a core requirement of the task is not yet satisfied: sorted_variables is defined but its "mutable" and "immutable" lists remain empty, so none of the 8 module-level variables are actually categorized by mutability as required [CHECKLIST ITEM #1#3]. In app/main.py, near the sorted_variables declaration, you should either directly assign all variables into the two lists (e.g. "mutable": [my_favourite_films, marks, collection_of_coins] and "immutable": [lucky_number, pi, one_is_a_prime_number, name, profile_info]) or call your check_mutability helper for each variable to populate the dict programmatically. Currently, check_mutability is never called, and its signature indicates dict | None but it does not return anything explicitly, which makes its behavior misleading; consider either returning the updated dict or changing the annotation to reflect that it mutates in place. There is also a linting blocker: on app/main.py:30, the parameter obj in check_mutability is missing a type annotation (ANN001), so add an appropriate type, for example def check_mutability(obj: object, sorted_dict: dict[str, list[object]]) -> dict[str, list[object]]: (or a more precise type if you prefer). Once you populate sorted_variables with all 8 variables and fix the type annotation issue, your solution should meet the functional expectations and pass the automated checks. You did a good job defining the variables and the IMMUTABLE_TYPES/MUTABLE_TYPES tuples, so you are close—focus on wiring up the helper (or direct assignment) and tightening the type hints to complete the task.


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

Important

Fix the issues, commit the changes, and then re-request my review using the Re-request review button2 in the Reviewers tab.

Tip

If you have any comments about this review, please leave a message in the Add a comment section below and mention me with the @mateacademy-ai-mentor tag3.
I will read your message during my next review of your pull request. Please do not reply directly to my comments, as that feature is not supported yet.

Caution

Do not close the pull request until the review is complete. Closing it early can lead to unexpected behavior and disrupt the review process.

Footnotes

  1. Rate AI review example

  2. Re-request AI review example

  3. Add AI review comments example

Comment thread app/main.py
Comment on lines +24 to +27
sorted_variables = {
"mutable" : [],
"immutable" : []
}
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

The sorted_variables dictionary is created here but both lists are empty. Per checklist items #1#3 you must place all 8 module variables into these lists, grouped by mutability. For this module those groupings should be roughly:

  • mutable: my_favourite_films, marks, collection_of_coins
  • immutable: lucky_number, pi, one_is_a_prime_number, name, profile_info
    You can either assign these lists directly or populate them programmatically.

Comment thread app/main.py Outdated
Comment on lines +30 to +34
def check_mutability(obj, sorted_dict : dict) -> dict | None :
if isinstance(obj, IMMUTABLE_TYPES):
sorted_dict["immutable"].append(obj)
elif isinstance(obj, MUTABLE_TYPES):
sorted_dict["mutable"].append(obj)
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

check_mutability appends objects to sorted_dict but is never called from this module, so sorted_variables remains empty. Also the function signature indicates a return type dict | None but there is no explicit return (it implicitly returns None). Either call this function for each variable (and/or have it return the dict) or remove it and populate sorted_variables directly.

Comment thread app/main.py
Comment on lines +21 to +22
IMMUTABLE_TYPES = (int, float, str, tuple, bool, bytes, frozenset)
MUTABLE_TYPES = (list, dict, set, bytearray)
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

IMMUTABLE_TYPES and MUTABLE_TYPES are defined and look appropriate for this task. Note (for awareness): bool is a subclass of int, but since bool is explicitly included in IMMUTABLE_TYPES this classification will work as intended.

Copy link
Copy Markdown

@mateacademy-ai-mentor mateacademy-ai-mentor left a comment

Choose a reason for hiding this comment

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

Review Summary

Your solution meets the functional requirements for this task: all eight module-level variables are defined, correctly categorized as mutable or immutable, and programmatically sorted into the sorted_variables dictionary using check_mutability as required. The helper function is properly annotated to return None and it mutates the sorted_variables structure in place, so it aligns with the expected behavior [CHECKLIST ITEM #6, #7]. There are no critical issues that would block correctness or test passing, so no changes are required for completion. As a minor improvement, you could make the sorted_dict parameter type more specific (for example, dict[str, list[object]]) to improve readability and static analysis. Another small refinement is to remove the print(sorted_variables) at the bottom of the file or guard it with if __name__ == "__main__": so importing the module doesn’t produce side-effect output. Overall, this is a solid implementation—nice work applying the mutability concepts and cleanly organizing the classification logic.


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

Footnotes

  1. Rate AI review example

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants