-
Notifications
You must be signed in to change notification settings - Fork 193
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
Latest patch breaking? #691
Comments
Yeah. New exports can be breaking. We should probably make a |
That's unfortunate but a necessary evil IMHO. I don't think we should tag a new breaking release. If StatsBase had reached 1.0, we wouldn't tag 2.0 because of a new export, just like Julia adds new exports in non-breaking release. I think the solution is to update Clustering ASAP and tag a new release there. |
Actually all that's needed is a tagging a new Distances release, since I had already merged a PR to fix the problem. This will also fix Clustering.jl tests (AFAICT it's only the testing code that broke, not the package code). See JuliaStats/Distances.jl#218. |
Fixed by JuliaRegistries/General#35908. |
I suspect the latest patch adding
pairwise
is breaking. For example, Clustering.jl is now failing tests:The text was updated successfully, but these errors were encountered: