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

Update approx to >=0.4, <0.6 to support approx 0.5 #1024

Closed
wants to merge 1 commit into from

Conversation

jturner314
Copy link
Member

@jturner314 jturner314 commented Jun 5, 2021

approx 0.5 updates its num-complex dependency to 0.4, which is the same version of num-complex which ndarray depends on. So, it's very useful for ndarray to support approx 0.5. Instead of expanding the range of the approx versions, another option would be to add a separate feature for approx 0.5, but I don't think the additional complexity would be worth it. When we release the next breaking release of ndarray, I think we should change this version specification to "0.5".

`approx` 0.5 updates its `num-complex` dependency to 0.4, which is the
same version of `num-complex` which `ndarray` depends on. So, it's
very useful for `ndarray` to support `approx` 0.5. Instead of
expanding the range of the `approx` versions, another option would be
to add another feature for `approx` 0.5, but I don't think the
additional complexity would be worth it. When we release the next
breaking release of `ndarray`, I think we should change this version
specification to "0.5".
@bluss
Copy link
Member

bluss commented Jun 5, 2021

Isn't the effect of this change de facto breaking, too?

@jturner314
Copy link
Member Author

jturner314 commented Jun 5, 2021

Huh, this approach doesn't work well. It seems that if a crate depends on ndarray (this branch) and approx 0.4, then Cargo handles this by using approx 0.5 for ndarray and approx 0.4 for the crate, even though both are compatible with approx 0.4. I thought that Cargo would use approx 0.4 for both ndarray and the crate in this case.

@jturner314
Copy link
Member Author

That's very unfortunate. It seems like the only non-breaking option is to add a separate feature for approx 0.5.

@jturner314
Copy link
Member Author

The approach in this PR doesn't work. I've created #1025 as a replacement.

@jturner314 jturner314 closed this Jun 5, 2021
@jturner314 jturner314 deleted the approx-0.5 branch June 5, 2021 01:08
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.

2 participants