fix(pandas v3): support pandas v3 by enforcing millisecond timestamp precision - #2724
fix(pandas v3): support pandas v3 by enforcing millisecond timestamp precision#2724haakonvt wants to merge 11 commits into
Conversation
There was a problem hiding this comment.
Code Review
This pull request standardizes the to_pandas export behavior across the SDK to use millisecond precision (datetime64[ms]) for timestamp and datetime columns, aligning with the Cognite API and ensuring compatibility with pandas v3. To eliminate duplicate conversion logic, CogniteResource.to_pandas now delegates to its corresponding list class via a new _LIST_CLASS class variable, with a fallback helper for resource types without a list counterpart. Custom to_pandas overrides (such as in Group and Instances) have been simplified or removed in favor of this unified delegation pattern, and meta-tests have been added to enforce the back-references between resource and list classes. No review comments were provided, so there is no feedback to assess.
867ada5 to
797e971
Compare
797e971 to
cf6d97b
Compare
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2724 +/- ##
==========================================
- Coverage 93.71% 93.69% -0.03%
==========================================
Files 504 504
Lines 51294 51476 +182
==========================================
+ Hits 48070 48229 +159
- Misses 3224 3247 +23
🚀 New features to boost your workflow:
|
No description provided.