singa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SINGA-460) Build packages for Py36 and Py37
Date Wed, 29 May 2019 15:11:00 GMT

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

ASF subversion and git services commented on SINGA-460:
-------------------------------------------------------

Commit 0a27ecf727fec16f15ed40ecffb52e4d51167465 in incubator-singa's branch refs/heads/master
from wang wei
[ https://gitbox.apache.org/repos/asf?p=incubator-singa.git;h=0a27ecf ]

SINGA-460 - Build packages for Py36 and Py37

Add py36 or py37 to the build string of conda packages
Update the docker file for conda build by removing cudnn


> Build packages for Py36 and Py37
> --------------------------------
>
>                 Key: SINGA-460
>                 URL: https://issues.apache.org/jira/browse/SINGA-460
>             Project: Singa
>          Issue Type: Improvement
>            Reporter: wangwei
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The conda packages for different py versions should have different names (build string).
Otherwise, the new submission to anaconda will overwrite the old submission, although they
are for different py versions.
>  
> This ticket is going to add py version into the build string to differentiate singa packages
built for different python versions.



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

Mime
View raw message