Hello, As you may know, Python 3 release introduced a break of compatibility with Python 2.7. Currently, Inkscape Python extensions (and the inkex.py file) is only compatible with Python 2. It is possible to make the code compatible with both versions, but some external modules (such as six or python-future) are necessary.
I think it is necessary to switch to a Python 3 compatible codebase, to attract new extensions developers, and for the ease of maintenance.
What is your opinion on this matter ?
Raphaël
Dear Raphaël:
I've actually been pushing for this change for quite some time now. When I first started writing Python code, it was in version 2, but I discovered version 3 on my own while trying to write other scripts independent of Inkscape - this is where I became a professional in the language.
We should definitely make the leap to Python 3, since it has innumerably more features and optimisations over Python 2. My SVG optimisation script, Rarify, and the Kinross vector library that it's a part of are in Python 3.5; many other scripts by other people use this same dialect. As a stretch goal, why not make it compatible with Python 4 as well when it comes out? All this will be good for Inkscape.
And I want it done before I'm admitted to Cambridge in August 2017.
Parcly Taxel, Princess of Science On 13 Mar 2016 18:54, "Raphaël Bournhonesque" <raphael0202@...48...> wrote:
Hello, As you may know, Python 3 release introduced a break of compatibility with Python 2.7. Currently, Inkscape Python extensions (and the inkex.py file) is only compatible with Python 2. It is possible to make the code compatible with both versions, but some external modules (such as six or python-future) are necessary.
I think it is necessary to switch to a Python 3 compatible codebase, to attract new extensions developers, and for the ease of maintenance.
What is your opinion on this matter ?
Raphaël
Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Hi, Great, but as I was mentioning in my previous message, we must introduce third party libraries in order to make the code compatible with both version of Python, and it would be great to have the opinion of the Inkscape community on the matter. And for Python 4 I'm not sure to understand what you are talking about, as the 3.6v is still in development, and I haven't heard of any compatibility break planned between v3 and v4. Best, Raphaël
On 13/03/2016 12:13, Jeremy Tan wrote:
Dear Raphaël:
I've actually been pushing for this change for quite some time now. When I first started writing Python code, it was in version 2, but I discovered version 3 on my own while trying to write other scripts independent of Inkscape - this is where I became a professional in the language.
We should definitely make the leap to Python 3, since it has innumerably more features and optimisations over Python 2. My SVG optimisation script, Rarify, and the Kinross vector library that it's a part of are in Python 3.5; many other scripts by other people use this same dialect. As a stretch goal, why not make it compatible with Python 4 as well when it comes out? All this will be good for Inkscape.
And I want it done before I'm admitted to Cambridge in August 2017.
Parcly Taxel, Princess of Science
On 13 Mar 2016 18:54, "Raphaël Bournhonesque" <raphael0202@...48... mailto:raphael0202@...48...> wrote:
Hello, As you may know, Python 3 release introduced a break of compatibility with Python 2.7. Currently, Inkscape Python extensions (and the inkex.py file) is only compatible with Python 2. It is possible to make the code compatible with both versions, but some external modules (such as six or python-future) are necessary. I think it is necessary to switch to a Python 3 compatible codebase, to attract new extensions developers, and for the ease of maintenance. What is your opinion on this matter ? Raphaël ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net <mailto:Inkscape-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Hi,
Le Mardi 15 mars 2016 19h23, Raphaël Bournhonesque <raphael0202@...2264.....> a écrit :
Great, but as I was mentioning in my previous message, we must introduce third party libraries in order to make the code compatible with both version of Python, and it would be great to have the opinion of the Inkscape community on the matter.
Note that we already use Six for the Scour external extension (see https://bugs.launchpad.net/inkscape/+bug/1411149). So we can rely on it to make our extensions Python3 compatible.
Regards, -- Nicolas
participants (3)
-
Jeremy Tan -
Nicolas Dufour -
Raphaël Bournhonesque