-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
include_string causes spurious AbstractRange deprecation warnings #24447
Comments
It looks like the problem may be related to the fact that you were using a deprecated version of julia> include_string("1+1")
WARNING: include_string(string) is deprecated, use `include_string(module, string)` instead.
Stacktrace:
[1] depwarn(::String, ::Symbol) at ./deprecated.jl:68
[2] include_string(::String) at ./deprecated.jl:1262
[3] eval(::Module, ::Expr) at ./repl/REPL.jl:3
[4] eval_user_input(::Any, ::Base.REPL.REPLBackend) at ./repl/REPL.jl:69
[5] macro expansion at ./repl/REPL.jl:100 [inlined]
[6] (::getfield(Base.REPL, Symbol("##1#2")){Base.REPL.REPLBackend})() at ./event.jl:95
in expression starting at no file:0
2 If you pass a module, do you still see a deprecation? julia> include_string(Main, "1+1")
2 I'm not sure why you'd be seeing the |
What's happening here is pretty weird, though it does ultimately relate to uses of The DataFrame constructor uses
|
Think this can be closed. |
On current DataFrames master there is an
include_string
call, which results inRemoving the call to
include_string
removes the deprecation warnings.The text was updated successfully, but these errors were encountered: