(2017-03-12, 08:25)arpitn30 Wrote: For now I'm focussing on both Python3 support and Kodi chromium browser and trying to understand the code before finalising for my proposal.

(2017-03-12, 08:25)arpitn30 Wrote: I just wanted to know if there is any documentation or list of features expected to be added in the Kodi browser?

(2017-03-12, 12:57)da-anda Wrote: as for Python3 - there is currently some work done to improve our interfaces and ease the way to integrate new languages.

(2017-03-14, 06:41)arpitn30 Wrote:

(2017-03-12, 12:57)da-anda Wrote: as for Python3 - there is currently some work done to improve our interfaces and ease the way to integrate new languages.

I'm a bit confused. Does the entire code base including system files, add-ons and the libraries for development has to be changed to be compatible with both Python 2.7 and Python 3.6 or we have to add the python3 support to the KODI api for script and plugin development. For the latter, the API will have to be shipped with both Python 2.7 and 3.6 interpreter as well as updated xmbc modules

(2017-03-14, 06:41)arpitn30 Wrote:

(2017-03-12, 12:57)da-anda Wrote: as for Python3 - there is currently some work done to improve our interfaces and ease the way to integrate new languages.

I'm a bit confused. Does the entire code base including system files, add-ons and the libraries for development has to be changed to be compatible with both Python 2.7 and Python 3.6 or we have to add the python3 support to the KODI api for script and plugin development. For the latter, the API will have to be shipped with both Python 2.7 and 3.6 interpreter as well as updated xmbc modules

(2016-12-15, 01:56)Hedda Wrote: Don't know about Kodi's core interface to Python, but as plain Python scripting language goes it should today be much smoother to upgrade to Python 3 and stay backwards compatible with Python 2 as there is now a new compatibility package that should make running Python 2 scripts under Python 3 easier.

Checkout: http://python-future.org/overview.html

Quote:python-future is the missing compatibility layer between Python 2 and Python 3. It allows you to use a single, clean Python 3.x-compatible codebase to support both Python 2 and Python 3 with minimal overhead.

It provides future and past packages with backports and forward ports of features from Python 3 and 2. It also comes with futurize and pasteurize, customized 2to3-based scripts that helps you to convert either Py2 or Py3 code easily to support both Python 2 and 3 in a single clean Py3-style codebase, module by module.

Notable projects that use python-future for Python 2/3 compatibility are Mezzanine and ObsPy.

As before it was adviced that if you upgraded to Python 3.x interpreter then you could still keep some backwards compatibility with Python 2.7 if you use the "six compatibility package" (for reference see http://packages.python.org/six/ ).

Now however the Python interpreter developers have made a new compatibility package that is called "python-future" (and it is also refered to as "future compatibility package"), so please see:

http://python-future.org/index.html ( and the actual package on GitHub https://github.com/PythonCharmers/python-future )

This "future compatibility package" is still in beta and doesn't support as many versions of Python as the six (it only goes back as far as Python 2.6, while six supports Python 2.4), but allows Python 2 compatible code to be written in a style that is closer to idiomatic Python 3 (for example, it includes an actual Python 2 compatible implementation of the Python 3 bytes type, rather than relying on the Python 2.x 8-bit string type that exposes a slightly different API).

Recommmed that you read both https://wiki.python.org/moin/Python2orPython3 and http://python-future.org/index.html

It suggest that much modern Python code should run largely unmodified on Python 3 using this "future compatibility package".

(2017-03-17, 12:12)Roman_V_M Wrote: Having both Python 2 and 3 interpreters (if it's possible at all) will be good because addons have been developed over the years by many authors, many of whom are not professional coders, so it's hard to expect them all to port their addons to Py3 or refactor to universal code. If we replace the interpreter, we will inevitably loose some addons because of compatibility issues.

The Standard Library aside, the main difference between Py2 and Py3 is clear separation between textual and byte strings. Currently, Kodi API functions that take textual data accept both str and unicode Py2 types. AFAIU unicode is transparently encoded to utf-8 by SWIG and passed as std:tring or char* to the Kodi core. In Py3 str type holds Unicode codepoints and bytes type is used for raw bytes. I thinks it would be totally OK if in Python 3 Kodi API functions would accept and return only str (that is, Unicode) data and not bytes.

Also, Kodi provides some binary Python libraries like PIL/Pillow that are compiled in place during Kodi building. Binary Python libraries must be compiled and linked against the target Python version, so I'm not sure if it is possible to have 2 versions of such libraries if we ever consider to support both Py2 and Py3.

(2017-03-17, 15:33)arpitn30 Wrote:

(2017-03-17, 12:12)Roman_V_M Wrote: Having both Python 2 and 3 interpreters (if it's possible at all) will be good because addons have been developed over the years by many authors, many of whom are not professional coders, so it's hard to expect them all to port their addons to Py3 or refactor to universal code. If we replace the interpreter, we will inevitably loose some addons because of compatibility issues.

The Standard Library aside, the main difference between Py2 and Py3 is clear separation between textual and byte strings. Currently, Kodi API functions that take textual data accept both str and unicode Py2 types. AFAIU unicode is transparently encoded to utf-8 by SWIG and passed as std:tring or char* to the Kodi core. In Py3 str type holds Unicode codepoints and bytes type is used for raw bytes. I thinks it would be totally OK if in Python 3 Kodi API functions would accept and return only str (that is, Unicode) data and not bytes.

Also, Kodi provides some binary Python libraries like PIL/Pillow that are compiled in place during Kodi building. Binary Python libraries must be compiled and linked against the target Python version, so I'm not sure if it is possible to have 2 versions of such libraries if we ever consider to support both Py2 and Py3.

Is it possible to migrate all the add-ons to python3 as well?
It could serve as a separate soc idea. There are around a 200+ python files in add-ons, it wouldn't be very hard to convert them using PyCharm and the futurise script. Although I've a vague idea to support the build time compile libraries, shipping both py2 and py3 interpreter would take a lot of space and quite possibly slow down the software as well.