Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: nuodb/nuodb-python
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: master
Choose a base ref
...
head repository: nuodb/nuodb-python
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: dbutson/datetime
Choose a head ref
  • 1 commit
  • 11 files changed
  • 1 contributor

Commits on Jun 24, 2025

  1. Support timezone-aware datetime objects 

    connection:
- Added support for explicit TimeZone connection property

datatype:
- Use Julian calendar for date/datetime before 1582 Oct 4.
  When the Gregorian calendar was introduced:
  .  The day after October 4, 1582 (Julian) became October 15, 1582 (Gregorian).
  .  That 10-day jump is not accounted for in C's calendar logic.
  .  Julian calendar handles leap years differently.
  The utc calendar the engine is using understands this the python functions
  based on C calendar logic do not.
- time.mktime , time.localtime don't support older dates while engine does
  changing to use calendar above and calculate time, avoid these issues.
- use of datetime + timezone should handle daylight savings times and not
  be off by an hour.

tests:
-  Use connection property TimeZone to change timezone
-  Support timezone-aware datetime
-  Use pytz correctly with localize if pytz is used
-  Use zoneinfo.ZoneInfo if available
-  added some more tests

encodedsession:
-  Manage and verify TimeZone settings on per connection basis
-  Allows connections with different TimeZone setting from same
   application

requirements.txt:
-  Add requirement for tzlocal and jdcal should be available on all
   supported python versions.  There is a change in
   api between releases , this is handled in the code.
    @butson
    butson committed Jun 24, 2025
    Configuration menu
    Copy the full SHA
    a1a4043 View commit details
    Browse the repository at this point in the history
Loading