On 02/22/2013 12:57 AM, Christian Ambros wrote:
Do I get this error because veusz isn't python3 ready?
Downloading v1.16 and installing it with python2.7 setup.py install
gives plenty of warnings concerning syntax changes due to the newer
versions of PyQt and C++ I use but finally installs it. Veusz 1.16 runs
great with 2.7 and I don't get any issues with console usage.
But since I have to use python3.x and there are some major difference I
like to use veusz with python3.
Will 2to3 may do the trick?
I think it's unlikely, mainly because of the difference in strings
between Python 2 and 3. There will be a lot of places in the code which
will need careful work in conversion. In addition the PyQt API is
different by default with Python 3, though there is a switch. It might
be easier to do the 2->3 and Python APIs separately.
It's quite a lot of work to move to Python 3. I also would rather not
have two versions of Veusz to maintain simultaneously, so it will
probably have to be one or the other. I also don't think it is practical
to have a version which can run under 2 and 3 simultaneously (event with
2to3). For example, the saved files will need some conversion as u''
doesn't work (although there was talk of fixing that).
I'm not sure of the correct timescale for any Python 3 port, as it will
take a lot of my little time away from adding features and fixing bugs.
There's also a question about how many people need the Python 2 version.
However, if you're using the embedding interface, it may be possible to
run Veusz under Python 2 and your code under Python 3. Only the
embedding interface itself needs conversion, because it uses a network
socket to communicate between the two ends.
Jeremy
_______________________________________________
Veusz-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/veusz-discuss
