singa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "wangwei (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SINGA-290) Upgrade to Python 3
Date Wed, 18 Apr 2018 14:15:00 GMT

    [ https://issues.apache.org/jira/browse/SINGA-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16442572#comment-16442572
] 

wangwei commented on SINGA-290:
-------------------------------

Would SWIG_PYTHON_2_UNICODE ([http://www.swig.org/Doc3.0/Python.html#Python_2_unicode)|http://www.swig.org/Doc3.0/Python.html#Python_2_unicode]
be better than SWIG_PYTHON_STRICT_BYTE_CHAR?
 string in python3 are unicode by default.
 string in python2 are then converted via SWIG_PYTHON_2_UNICODE

> Upgrade to Python 3
> -------------------
>
>                 Key: SINGA-290
>                 URL: https://issues.apache.org/jira/browse/SINGA-290
>             Project: Singa
>          Issue Type: Improvement
>            Reporter: Moaz Reyad
>            Priority: Major
>
> Currently SINGA supports Python 2.7, we need to upgrade to Python 3.
> One reason for this upgrade is related to SINGA-274, where new Debian packages are required
to use Python 3 according to Debian packaging policy on Python:
> https://www.debian.org/doc/packaging-manuals/python-policy/ch-python3.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message