John Hunter wrote:
>>"Bryan" == Bryan Cole <[EMAIL PROTECTED]> writes:
>
>
> Bryan> MPL uses CXX instead of SWIG; I'm no C++ export so I havn't
> Bryan> looked at adding __get/setstate__ functions to the objects
> Bryan> themselves. copy_reg is nice because you can add
>
> Actual
> "Bryan" == Bryan Cole <[EMAIL PROTECTED]> writes:
Bryan> MPL uses CXX instead of SWIG; I'm no C++ export so I havn't
Bryan> looked at adding __get/setstate__ functions to the objects
Bryan> themselves. copy_reg is nice because you can add
Actually, most of the mpl extension code
On Sun, 2006-06-18 at 15:38 +1000, John Pye wrote:
> FWIW I found that I was able to pickle C++ objects but simply adding
> python methods __reduce__ and __setstate__ in my SWIG .i file -- I'm not
> sure if Matplotlib uses this approach or not. I didn't need to use
> copy_reg (perhaps it's preferab
FWIW I found that I was able to pickle C++ objects but simply adding
python methods __reduce__ and __setstate__ in my SWIG .i file -- I'm not
sure if Matplotlib uses this approach or not. I didn't need to use
copy_reg (perhaps it's preferable? I don't know)
http://freesteam.cvs.sourceforge.net/fre
On Sun, 2006-06-18 at 00:05 +1000, John Pye wrote:
> Hi all,
>
> A thought just occurred to me: I wonder if it would be useful to be able
> to 'pickle' Matplotlib plots, using the python cPickle library. This
> way, I could save my plots in a form that would allow me to load them
> back later (wit
Hi all,
A thought just occurred to me: I wonder if it would be useful to be able
to 'pickle' Matplotlib plots, using the python cPickle library. This
way, I could save my plots in a form that would allow me to load them
back later (with just the necessary source data) and fiddle with things
like t
