Remove Reason.ACQUIRE and Reason.RELEASE

[Jc2k]

What do these changes do?

In #258 we talked about how there was a bit of a chicken and the egg situation with requires_finalizer. You proposed pulling the the requires_finalizer detection into handle_resource_changing_cause (option B).

This pull request implements option B from that discussion, as I understood it.

Description

The need to add or remove a handler was detected in detect_resource_changing_cause in causation.py.

The need to add or remove a handler will be detected in handle_resource_changing_cause in handling.py.

N/A

Internal.

@nolar presented 2 possible options in another PR, this is the 2nd option.

Not that I can see, but i am not familiar with this code.

Issues/PRs

Issues:

Related:

#258

Type of changes

• Refactoring (non-breaking change which does not alter the behaviour)

Checklist

• The code addresses only the mentioned problem, and this problem only
• I think the code is well written
• Unit tests for the changes exist
• Documentation reflects the changes
• If you provide code modification, please add yourself to CONTRIBUTORS.txt

[zincr]

🤖 zincr found 1 problem , 0 warnings

❌ Specification
✅ Large Commits
✅ Approvals
✅ Dependency Licensing

Details on how to resolve are provided below

---

Specification

All pull requests must follow certain rules for content length and form

Please ensure the follow issues are resolved:

• ✅ Pull Request Title must be atleast 8 characters
• ✅ Pull Request body must be atleast 8 characters
• ❌ Pull Request body must contain issue number
   

[nolar]

@Jc2k Thanks for this PR. I guess, it now unblocks the way for the callback-filtering.