[
https://issues.apache.org/jira/browse/CLIMATE-866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15590934#comment-15590934
]
Alex Goodman commented on CLIMATE-866:
--------------------------------------
One minor point, I only submitted a build for Python 2.7 on conda-forge for now
since version 1.1 isn't Python 3 compatible. When we are ready to release 1.2.0
we can then allow for Python 3 builds. Additionally AFAIK Python 3.4 and 3.5
can be built by conda-forge, but not 3.3.
> Create ocw conda package against Python3.x as well as Python 2.7
> ----------------------------------------------------------------
>
> Key: CLIMATE-866
> URL: https://issues.apache.org/jira/browse/CLIMATE-866
> Project: Apache Open Climate Workbench
> Issue Type: Task
> Components: conda
> Affects Versions: 1.1.0
> Reporter: Lewis John McGibbney
> Assignee: Alex Goodman
> Priority: Critical
> Fix For: 1.2.0
>
>
> Hi [~agoodman], I recently tried to use the conda package to install OCW. I
> am using Miniconda3 and therefore Python3. When I run the conda install, I
> get the following
> {code}
> lmcgibbn@LMC-032857 /usr/local/climate(master) $ conda install -c agoodman ocw
> Fetching package metadata .........
> Solving package specifications: ....
> The following specifications were found to be in conflict:
> - ocw
> - python 3.5*
> Use "conda info <package>" to see the dependencies for each package.
> {code}
> This is because the packages are built using Python 2.7 as per
> https://anaconda.org/agoodman/ocw/files.
> Seeing as all of our CI and smoke testing now runs off of Python 3.X, I
> wonder if you are able to push an update to the conda files which compile
> against Python3?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
