Allow opting in to treat datetimeus as datetime rather than DatetimeUS

Open
#80 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
databases

Research direction

Start by locating where the Python API maps the database type datetimeus to DatetimeUS, then inspect any related tests or type-handling entry points. Done means a documented opt-in for new applications or databases that treats datetimeus as datetime without changing the existing default behavior.

Written by the indexing model from the issue text.

Description

For new applications/databases it might make sense to not have to deal with this historic artifact. DatetimeUS can trip up some downstream libraries like pydantic/fastapi.

Dominant language
Python
Stars
29
Forks
28
Avg merge
11h 25m
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bloomberg/python-comdb2

All issues in bloomberg/python-comdb2

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.