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

precompile and PyCall, method error for | #280

Closed
jverzani opened this issue May 24, 2016 · 2 comments
Closed

precompile and PyCall, method error for | #280

jverzani opened this issue May 24, 2016 · 2 comments

Comments

@jverzani
Copy link
Contributor

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
@stevengj
Copy link
Member

The PyTypeObject constructor has just changed in #279 ... can you see if your problem still occurs with the latest master?

@jverzani
Copy link
Contributor Author

Thanks! It is working now with the latest master.

On Tue, May 24, 2016 at 8:19 AM, Steven G. Johnson <[email protected]

wrote:

The PyTypeObject constructor has just changed in #279
#279 ... can you see if your
problem still occurs with the latest master?


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#280 (comment)

John Verzani
Chair, Department of Mathematics
College of Staten Island, CUNY
[email protected]

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

No branches or pull requests

2 participants