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
Fix depwarn on 0.5 #267
Fix depwarn on 0.5 #267
Conversation
@@ -1,4 +1,4 @@ | |||
julia 0.4 | |||
Compat 0.7.14 | |||
Compat 0.7.14+ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Presumably we should wait until the necessary version of Compat is tagged?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct. I'm just not sure what's the status of JuliaLang/Compat.jl#192 .
General comment about passing julia object to C.
The name of the |
Oh, right. The |
Another note is that |
It's true that it can return whatever type it feels like as long as it keeps the result of |
Yeah, using |
Travis failure:
Probably the string conversion needs to be: function PyObject(s::AbstractString)
sb = String(s)
if pyunicode_literals || !isascii(sb)
PyObject(@pycheckn ccall(@pysym(PyUnicode_DecodeUTF8),
PyPtr, (Ptr{UInt8}, Int, Ptr{UInt8}),
sb, sizeof(sb), C_NULL))
else
PyObject(@pycheckn ccall(@pysym(PyString_FromStringAndSize),
PyPtr, (Ptr{UInt8}, Int), sb, sizeof(sb)))
end
end and you can get rid of |
............ python unicode coupled with julia string change ........... Yeah, I only tested on python3.... I'll fix it soon. |
String, Symbol, precision(BigFloat) Also fix an incorrect use of unsafe_convert
Done |
ping. |
Thanks! |
String
,Symbol
,precision(BigFloat)
Also fix an incorrect use of
unsafe_convert
.Requires a new tag of
Compat
.Also includes #260
Requires JuliaLang/Compat.jl#192