PolicyEngine / PolicyEngine/policyengine-core
Fix newly added enum.py statement to eliminate FutureWarning of deprecation
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 22
- Forks
- 30
- Avg merge
- 14h 33m
- Merged PRs (30d)
- 7
Description
@nikhilwoodruff, a few days ago in commit https://github.com/PolicyEngine/policyengine-core/pull/231/commits/7598d96af1c27855d594ed5575e4979eaf944539 you added this statement:
This statement generates a dozen FutureWarnings of a deprecation as described here:
It would be good to fix this before it becomes an error.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting policyengine_core/enums/enum.py around lines 56–57 and reproduce the FutureWarnings caused by the statement added in commit 7598d96af1c27855d594ed5575e4979eaf944539. Update that statement so the deprecation warning no longer occurs, then verify the warnings are eliminated before the deprecation becomes an error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100