Re: [matplotlib-devel] mpl release candidate branch

[Benjamin R. <ben...@ou...>]

On Friday, September 23, 2011, Michael Droettboom <md...@st...> wrote:
> I haven't seen any of these warnings: DeprecationWarnings and
PendingDeprecationWarnings are supposed to be turned of by default in a
vanilla Python build.  However, I'm familiar with the PyCObject/PyCapsule
issue from working on the matplotlib-py3 branch.
>
> The py3 branch has changes to the local copy of PyCXX to use PyCapsule
instead of CObject, since 3.2 has removed CObject altogether [1].  However,
these changes were made to the Python 3 side of PyCXX only -- Python 2.6 and
earlier need to continue to support PyCObject, and Python 2.7 still has
PyCObject, so it didn't seem worth the effort.  I missed that Python 2.7 has
a PendingDeprecationWarning on for these things.  I guess we should probably
make the analogous changes to the Python 2 side (inside of #ifdef's so
Python 2.6 and earlier continue to use PyCObject).  It should be pretty
straightforward to do, but I won't have a chance until Monday.
>
> [1]
https://github.com/matplotlib/matplotlib-py3/commit/86a34cab1a005f9bb0d9c2a1b57b3e41fa32064a#comments
 <
https://github.com/matplotlib/matplotlib-py3/commit/86a34cab1a005f9bb0d9c2a1b57b3e41fa32064a#comments
>
>
> I submitted these changes upstream to Barry Scott, but it doesn't look
like they've made it into the PyCXX SVN repository yet.
>
> Mike

Personally, my vote is to live with the deprecation warnings.  They only
happen if you turn warnings on in python 2.7 (by default, they are off).  I
am not that comfortable with such a change this close to release for a minor
issue (unless I am missing something..?)

Ben Root