You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think this is a different issue than #269. Sometime in the past 13 days, something has changed so that PyCall doesn't precompile. Here is the error I get after running Pkg.update() on a just downloaded nightly (Commit a0661a0 (0 days old master))
julia> using PyCall
INFO: Recompiling stale cache file /Users/verzani/.julia/lib/v0.5/PyCall.ji for module PyCall.
... cut out warnings on bytestring and WORD_SIZE ....
ERROR: InitError: MethodError: no method matching |(::UInt32, ::Void)
Closest candidates are:
|(::Any, ::Any, ::Any, ::Any...)
|(::BinDeps.SynchronousStepCollection, ::Any)
|{T<:Union{Int128,Int16,Int32,Int64,Int8,UInt128,UInt16,UInt32,UInt64,UInt8}}(::T<:Union{Int128,Int16,Int32,Int64,Int8,UInt128,UInt16,UInt32,UInt64,UInt8}, ::T<:Union{Int128,Int16,Int32,Int64,Int8,UInt128,UInt16,UInt32,UInt64,UInt8})
...
in PyCall.PyTypeObject(::String, ::Int64, ::PyCall.##20#21) at /Users/verzani/.julia/v0.5/PyCall/src/pytype.jl:270
in pyjlwrap_init() at /Users/verzani/.julia/v0.5/PyCall/src/pytype.jl:387
in __init__() at /Users/verzani/.julia/v0.5/PyCall/src/pyinit.jl:100
in _require_from_serialized(::Int64, ::Symbol, ::String, ::Bool) at ./loading.jl:174
in _require_from_serialized(::Int64, ::Symbol, ::Bool) at ./loading.jl:202
in require(::Symbol) at ./loading.jl:332
in eval(::Module, ::Any) at ./boot.jl:225
in macro expansion at ./REPL.jl:92 [inlined]
in (::Base.REPL.##1#2{Base.REPL.REPLBackend})() at ./event.jl:46
during initialization of module PyCall
The text was updated successfully, but these errors were encountered:
I think this is a different issue than #269. Sometime in the past 13 days, something has changed so that PyCall doesn't precompile. Here is the error I get after running
Pkg.update()
on a just downloaded nightly (Commit a0661a0 (0 days old master))The text was updated successfully, but these errors were encountered: