NatLabRockies / NatLabRockies/chronify
Some time zones pass is_standard_time_zone for some years but not others
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
For example, Asia/Colombo failed for 1996 after its "is a standard time" status was only checked for 2020.
Contributor guide
No contributing guide indexed for this repository
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 reproducing the Asia/Colombo result for 1996 and comparing it with 2020, using the existing time-zone validation entry point described by the issue. Trace how is_standard_time_zone determines a zone's status across years. Done means the check gives consistent, year-appropriate results for Colombo and the regression is covered by a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- internationalization
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100