Skip to content

Conversation

@bstaletic
Copy link
Collaborator

@bstaletic bstaletic commented Feb 23, 2021

Description

this is an attempt to fix #2861

Suggested changelog entry:

Allow negative timedelta values to roundtrip.

@bstaletic bstaletic force-pushed the chrono branch 2 times, most recently from a4932c1 to ac694fc Compare February 24, 2021 10:33
@YannickJadoul
Copy link
Collaborator

For the record and future reference: #2861 discusses all of this in great detail, why the current approach is an issue and how this simple change fixes things (and should cause any further issues?).

@rwgk
Copy link
Collaborator

rwgk commented Mar 8, 2021

LGTM and I ran this through our Google-global testing (just be cause it's easy and highly conclusive). Thanks @bstaletic!

@rwgk rwgk merged commit f110889 into pybind:master Mar 8, 2021
@github-actions github-actions bot added the needs changelog Possibly needs a changelog entry label Mar 8, 2021
@knzivid
Copy link
Contributor

knzivid commented Mar 8, 2021

@YannickJadoul Which next release version is this PR going into?

@rwgk
Copy link
Collaborator

rwgk commented Mar 8, 2021

This was merged into master. We're aiming for a 2.7 release (sorry the dev tag is currently misleading). We don't have a fixed date for the next release. I do not think the internals version will increase. You should be able to use current master in combination with other pybind11 extensions built against stable. master is extremely well tested these days.

@henryiii henryiii removed the needs changelog Possibly needs a changelog entry label Jul 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[QUESTION] Chrono bindings and negative datetime.timedelta

5 participants