Separate pd2.NaT for datetime vs timedelta · Issue #74 · wesm/pandas2 (original) (raw)
Navigation Menu
- GitHub Copilot Write better code with AI
- GitHub Advanced Security Find and fix vulnerabilities
- Actions Automate any workflow
- Codespaces Instant dev environments
- Issues Plan and track work
- Code Review Manage code changes
- Discussions Collaborate outside of code
- Code Search Find more, search less
Explore - Why GitHub
- All features
- Documentation
- GitHub Skills
- Blog
- By company size
- Topics
- Pricing
Provide feedback
We read every piece of feedback, and take your input very seriously.
Include my email address so I can be contacted
Saved searches
Use saved searches to filter your results more quickly
Appearance settings
This repository was archived by the owner on Apr 10, 2024. It is now read-only.
Notifications You must be signed in to change notification settings
Additional navigation options
This repository was archived by the owner on Apr 10, 2024. It is now read-only.
Open
Open
Separate pd2.NaT for datetime vs timedelta
#74
Description
opened
A lot of headaches are caused by the fact that pd.NaT is usually a datetime but occasionally a timedelta. In some cases this leads to unavoidable internal inconsistency (pandas-dev/pandas#19124). For pandas2 it is worth consider breaking these into two distinct constants with unambiguous types.
Metadata
Metadata
Assignees
No one assigned
Labels
No labels
No labels
Projects
No projects
Milestone
No milestone
Relationships
None yet
Development
No branches or pull requests