Simon,
Thanks for looking into that!
Steven, what are your plans for bumping PyCall to the next version number?
Best,
John
On Sunday, January 4, 2015 6:39:33 PM UTC-5, Simon Kornblith wrote:
https://github.com/stevengj/PyCall.jl/pull/110
On Sunday, January 4, 2015 9:34:14 AM UTC-5, John
Steven,
How difficult would it be to work a way to suppress this warning message? I
general I would argue that it's best to avoid printing warnings to the
screen unless there is something going on to be genuinely warned about, so
as not to confuse the end-user. Since my package
https://github.com/stevengj/PyCall.jl/pull/110
On Sunday, January 4, 2015 9:34:14 AM UTC-5, John Zuhone wrote:
Steven,
How difficult would it be to work a way to suppress this warning message?
I general I would argue that it's best to avoid printing warnings to the
screen unless there is
Also encountered it. Same question as op asked.
On Sunday, February 23, 2014 6:47:55 AM UTC-8, Uwe Fechner wrote:
Hello,
if I enter:
using PyCall
@pyimport pylab as plt
I get the warning:
Warning: imported binding for transpose overwritten in module __anon__
I am using Julia 0.21 on
You can safely ignore it. @pyimport creates an module __anon__ (which is
assigned to plt in this case) that has definitions for the Python functions
in the Python module. The warning is telling you that this module creates
its own transpose function instead of extending Base.transpose. (It
This also comes up in the SymPy package
(https://github.com/jverzani/SymPy.jl), would like to know what's causing
it.
On Sunday, February 23, 2014 9:47:55 AM UTC-5, Uwe Fechner wrote:
Hello,
if I enter:
using PyCall
@pyimport pylab as plt
I get the warning:
Warning: imported binding
