Hi Hazen: P.S. This further comment assumes that generating a python3 binding is fairly trivial, i.e., nothing much more than using the -py3 option to swig. If your experiments confirm that assumption holds, then I suggest you should define a CMake option called PLPLOT_USE_PYTHON3. If the user sets that to ON, the build system generates and uses a python3 binding (using, e.g., that -py3 option to swig), and if OFF it generates and uses a python2 binding (which we will likely want to support indefinitely in any case). With that either/or organization between the two cases, the names of the modules we build will be identical in the two cases, and the examples should just work regardless of whether the binding is python2 or python3 (assuming you can convert the syntax of the examples so that they work both with python-2.7 and python-3.0).
Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------------------------------------------------------ _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
