[issue35357] unittest.mock.call can't represent calls to a method called 'parent'

Change by Andrew Dunai : -- keywords: +patch pull_requests: +10110 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue35357> ___ ___ Py

[issue35357] unittest.mock.call can't represent calls to a method called 'parent'

Andrew Dunai added the comment: I was considering wrapping a `unittest.mock._Call` class definition within a function that would contain name & parent as local variables (arguments). Thus they would be accessible within the `_Call` class, but wouldn't be accessible from the outside

[issue35357] unittest.mock.call can't represent calls to a method called 'parent'

Andrew Dunai added the comment: I see 2 most applicable ways to do it: - Hide .parent and .name by mangling - Define them within the mock class definition scope, but not within the class itself. As long as those are accessed only from within the mock class, I think second method would be

[issue35357] unittest.mock.call can't represent calls to a method called 'parent'

Andrew Dunai added the comment: I've just stumbled upon this issue while looking for a good first issue to contribute on. If the community agrees this is something that needs to be done, I'll gladly work on this. -- nosy: +and3rson

[issue29249] Pathlib glob ** bug

Andrew Dunai added the comment: Isn't this intended? According to https://docs.python.org/2/library/glob.html and wiki, typical UNIX glob pattern does not have the reqursive matching operator (`**`). -- nosy: +Andrew Dunai ___ Python tracker