On 2017-04-22 17:55-0400 Hazen Babcock wrote:
> On 04/21/2017 03:42 AM, Alan W. Irwin wrote:
>>
>> Hi Hazen:
>>
>> Could you please test commit 578b028?
[...]
> It works for me with Python3 and pyqt5.
Hi Hazen:
That positive test result on your Linux platform is a big relief to
me. I
On 04/21/2017 03:42 AM, Alan W. Irwin wrote:
Hi Hazen:
Could you please test commit 578b028? For that commit I made some
modest progress with Python 3 for both pyqt4 and pyqt5, but I have hit
a roadblock with a run-time error saying the plplot_pyqt[45] extension
modules are not initialized
On 2017-04-17 16:30-0700 Alan W. Irwin wrote:
> Note also that there are additional non-standard Python examples in
> the examples/python subdirectory so those should all be checked to
> make sure they work with both Python 2 and Python 3. And similarly
> for the pyqt4 and pyqt5 standard
On 12/01/2016 04:13 AM, Alan W. Irwin wrote:
>> Spoke too soon I guess. It appears that swig detects which version of
>> Python you are using and creates a binding that only works with that
>> version. So if you create the bindings in a Python3 environment they
>> will not work with Python2 and
On 2016-11-30 20:59-0500 Hazen Babcock wrote:
>
>
> On 11/27/2016 01:40 PM, Alan W. Irwin wrote:
>> It is good to hear it is likely going to be even easier than I thought. I
>> guess that -py3 flag is needed for more complex Python bindings than ours.
>
> Spoke too soon I guess. It appears that
On 11/27/2016 01:40 PM, Alan W. Irwin wrote:
> It is good to hear it is likely going to be even easier than I thought. I
> guess that -py3 flag is needed for more complex Python bindings than ours.
Spoke too soon I guess. It appears that swig detects which version of
Python you are using and
On 2016-11-27 10:19-0500 Hazen Babcock wrote:
> On 11/27/2016 02:51 AM, Alan W. Irwin wrote:
>>
>> 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
On 11/27/2016 02:51 AM, Alan W. Irwin wrote:
>
> 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
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
Hello,
I would like to fix PLplot so that it works with Python3. At a minimum
it looks like this means fixing all the print statements, i.e.:
print "asdf" -> print("asdf")
I'll test against Python2.7. Do I also need to test against Python2.6?
Or is that far enough in the past that we don't
On 2010-10-27 09:41-0600 Orion Poplawski wrote:
Has any thought been given to supporting python3? Fedora now ships python3
alongside python and numpy now has a python3 module.
Hi Orion:
Your question inspired me to google for python2 versus python3
differences, and I found
11 matches
Mail list logo
