Now that #517 is merged, there are a few things remaining to do before we try to move all PyCall users to the new interface.
First, we need to deprecate some more things (probably in a "1.9" release or similar) to help with the transition:
Some other things I would like to change/fix during the big transition:
Now that #517 is merged, there are a few things remaining to do before we try to move all PyCall users to the new interface.
First, we need to deprecate some more things (probably in a "1.9" release or similar) to help with the transition:
@pyimportandpywrap— just dopyimportnow. deprecate pywrap #633getindex(::PyObject, ::Integer)and similar — these will stop subtracting 1 in PyCall 2.0, so they will have to be deprecated for now. deprecate o[integer] so that we can transition to 0-based access #632Some other things I would like to change/fix during the big transition:
PyVector, dictionaries toPyDict, and NumPy arrays toPyArrayby default, but don't convert subclasses of these? (see RFC: Lazier and more interface-based conversion #617)PyPtrto see if they needGC.@protectfor gc safety. be more careful about potential gc of pyptrs #630