[
https://issues.apache.org/jira/browse/CLIMATE-866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15473118#comment-15473118
]
Alex Goodman commented on CLIMATE-866:
--------------------------------------
Hi [~lewismc],
Yep, this can easily be done by adding an additional flag to specify python
versions when executing {{conda build}}. I'll get to this right away tomorrow
morning. AFAIK this shouldn't warrant any changes to the recipe files but it
will nonetheless make maintaining the packages more cumbersome if we wish to
support both python2 and 3. Perhaps I should just make a python or bash shell
script that automates a lot of this since it's mostly just a matter of chaining
a bunch of {{conda build}} commands together.
> Create conda packages against Python3
> -------------------------------------
>
> 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)
