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

Neither advertise the functions moved to StatsBase nor test them on 0.7 #559

Merged
merged 1 commit into from
May 30, 2018

Conversation

martinholters
Copy link
Member

These functions call through to Base functions, which is rendered impossible after their moval to StatsBase (JuliaLang/julia#27152). As StatsBase is using Compat, Compat cannot use StatsBase. In the future, these functions should print deprecation warnings also on 0.6, telling people how to get the desired functionality, once that is settled (see discussion in JuliaStats/StatsBase.jl#379).

Alternatively, we could duplicate the code now moved to StatsBase in Compat.

@martinholters
Copy link
Member Author

BTW, what works right now (well, with sufficiently recent StatsBase) is this e.g. pattern:

if VERSION < v"0.7.0-DEV.5238"
    y = Compat.varm(...)
else
    y = StatsBase.varm(...)
end

I don't think that is something we should be advertising, though.

@martinholters
Copy link
Member Author

Known unrelated OSX failure.

@nalimilan
Copy link
Member

Maybe we should still run the tests on Julia 0.6? Packages can already rely on these functions and we really don't want to break them there.

@martinholters
Copy link
Member Author

True. OTOH, once JuliaStats/StatsBase.jl#382 has landed, I'd add deprecation warnings here to make people switch to StatsBase.StatsCompat, and we usually don't test deprecated functionality. But for the time being, keeping the tests behind a VERSION conditional surely doesn't do any harm.

These functions call through to Base functions, which is rendered
impossible after their moval to StatsBase (JuliaLang/julia#27152). As
StatsBase is using Compat, Compat cannot use StatsBase. In the future,
these functions should print deprecation warinings also on 0.6, telling
people how to get the desired functionality, once that is settled.

Alternatively, we could duplicate the code now moved to StatsBase in
Compat.
@martinholters
Copy link
Member Author

martinholters commented May 30, 2018

Barring objections, I'll merge later today.

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.

None yet

2 participants