Data structure: Linked list

[Vlad421]

• cleaned typos in heap_sort

• [x] PR's title includes the challenge's name and language
• [x] PR has short and clear description of the challenge
• [ ] PR has appropriate labels and milestones for easy identification
• [ ] PR it is assigned to the owner
• [ ] reviewers are assigned
• [ ] the PR contributes only one focused change
• [ ] the branch is up to date with main/master
• [ ] the code works when pulled and run locally
• [ ] all conflicts are resolved (if any)
• [ ] It is linked to an issue in the appropriate column of the project board
• [ ] feedback is addressed (if any, and if it is appropriate feedback.)

README Documentation

• [x] The solution is documented in /src/README.md
• [x] The markdown source is formatted
• [x] Spelling and grammar is correct in all text
• [x] The markdown looks correct when you preview the file
• [x] All links and images work
• [x] The README documents the solution's behavior, strategy(ies) and implementation(s)
• [ ] There are use cases in code blocks to illustrate the function's behavior

Python Files

• [x] There is a module header
• [x] There is a module docstring
• [x] File names are in snake_case
• [ ] Test files are named test_<module_name>.py

Function Docstring

• [x] Behavior description
• [ ] Parameter description
• [ ] Return value description
• [ ] Include any assumptions
• [ ] Include 3 or more (passing!) doctests
• [ ] Include 1-2 use cases (if necessary)

Function Implementation

• [x] The solution is not is not copied from djeada
• [x] The code is auto-formatted
• [x] The code has no (reasonable) linting mistakes
• [x] Variables are named with snake_case
• [x] The function has a clear and helpful name
• [x] The file's name matches the function name
• [x] The code follows the strategy as simply as possible
• [x] Variable names are clear and helpful
• [x] Comments explain the strategy (if necessary)
• [x] There are type annotations
• [ ] (challenge) The code includes defensive assertions

Unit Test Suite

• [x] The test class has a helpful name in PascalCase
• [ ] The test class has a docstring
• Each unit test has
  • [x] A helpful name
  • [ ] A clear docstring
  • [ ] Only one assertion
• [x] All tests pass
• [ ] There are tests for defensive assertions
• [ ] There are tests for boundary cases
• [ ] Test suite includes black-box and glass-box tests

[Vlad421]

You forgot the dot between LinkedList and __data Should be like this:

self.assertEqual(linked_list._LinkedList.__data[0].value

Also you shouldn't be able to access the __data variable it's private. But who knows. Python has its flaws

[tvsirius]

python kind of like 'protect' marked with variables, but you still can access them with this constrution self.assertEqual(linked_list._LinkedListdata[0].value, 1) self.assertEqual(linked_list._LinkedListdata[0].next.value, 3)

run this code

MyClass.__protected - will give no access MyClass._MyClass__proctected - will give access

[Vlad421]

python kind of like 'protect' marked with variables, but you still can access them with this constrution self.assertEqual(linked_list._LinkedListdata[0].value, 1) self.assertEqual(linked_list._LinkedListdata[0].next.value, 3)

run this code

MyClass.__protected - will give no access MyClass._MyClass__proctected - will give access

Indeed. You can access private vars through this construction.

Fixed issue.