Support date-specific utility methods
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by reading the existing date-type support in cfpint and comparing the relevant operations and API details in cf_units and cftime. Define the behavior and naming for num2date, date2num, and is_date, including calendar handling, then add documentation and tests that establish the chosen public API.
Written by the indexing model from the issue text.
Description
It would seem that, as we explcitly support date-type methods, we should back that up with convenience methods like the ones in cf_units. Probably at least :
- num2date
- date2num
- is_date
I.E. we could just require the user to use cftime directly,
but it is probably both more convenient and clearer to expose the operations directly in cfpint.
We don't necessarily want to copy the names or all API details from cf_units / cftime.
In fact, it is probably clearer not to. Cf. cf_unit "calendar" vs cfpint "calendar_string"
(aside: calendar_string is probably better called "calendar_name" -- see #6 )
- Dominant language
- Python
- Stars
- 1
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from SciTools/cfpint
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Similar issues
-
kind/bug priority/medium qa_automation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
yugabyte/yugabyte-db#37324 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 87/100
btclib-org/btclib-node#2260 ·
Maintainers usually reply within 1 day
-
ChatBedrockConverse changes the keys of JSON tool results to camelCase (`order_id` becomes `orderId`)Possibly taken @geyazheng claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
langchain-ai/langchain-aws#1469 ·
Maintainers usually reply within 1 day
-
GCToggler leaves collection enabled if the body re-enables itPossibly taken @Gambit-Checkmate claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 7 days
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day