I don't know if @happyleavesaoc wants to merge this, but there are many unrelated changes like replacing single quotes with double quotes and even some code changes.

I don't know if @happyleavesaoc wants to merge this, but there are many unrelated changes like replacing single quotes with double quotes and even some code changes.

I was trying to minimize the code changes but sometimes it would say that the code changed but after checking the original version the code was the same with the same indentation

Hello, I'm interested in accepting a PR with some docstring updates, but I think the following would be necessary:

1. no unrelated style changes (this will make your diff a lot more legible)
2. docstrings should be value-add rather than a restatement of the code - for example, setters and getters don't need explanation
3. avoid class-level enumeration of attributes and methods (harder to maintain)
4. type info should be in the form of type hints

I'll keep it in mind and try to update the pr with these fixes

@happyleavesaoc Should i open a new pr with only the new docstrings or just update this one?

@chicco-carone either way is fine

If there are any issues with the pr so that it can't be merged just let me know and i'll try to fix them