Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid union when intervals share a bound, one open and one closed #12

Closed
AlexandreDecan opened this issue Sep 11, 2019 · 2 comments
Closed
Labels
bug Something isn't working

Comments

@AlexandreDecan
Copy link
Owner

Unioning AtomicInterval instances (and by extension Interval instances) can lead to an invalid result if the two intervals share a (lower or upper) bound, where one is open and the other one is closed.

>>> I.closed(0, 2) | I.open(0, 2)
I.open(0, 2)

... where the expected result is I.closed(0, 2).

@AlexandreDecan
Copy link
Owner Author

This issue is fixed in the master branch, and the fix will be part of 1.9.0 update or, if I cannot manage to release this version soon, will be hotfixed in 1.8.1.

@AlexandreDecan
Copy link
Owner Author

Fixed in 1.9.0, now available on PyPI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant