Drop policy compat32
Open
enhancement
- Dominant language
- Python
- Stars
- 45
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
I think we should consider dropping the compat32 policy as an option.
It is designed for backwards compatibility, including bugs.
Given that Foal does not promise full compatibility with previous versions, I don't think we need to support it.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue does not identify a file, test, or entry point for the compat32 policy. First locate where the policy is defined and consumed, then determine the compatibility implications and affected tests; done means the option is removed without breaking the supported policy behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100