search

pyne / pyne-ci

Continuous Integration scripts for PyNE core using Batlab
Other
1 stars 5 forks source link

add python 3 build #18

Closed crbates closed 9 years ago

crbates commented 9 years ago

also update moab to 4.6.3

crbates commented 9 years ago

@gidden or @scopatz could you check over this when you get a chance.

scopatz commented 9 years ago

Hopefully @gidden or @elliottbiondo can, I don't plan on sleeping because of cyclus until the 24th :)

makeclean commented 9 years ago

Cameron

Could you go straight to version 4.7.0 of moab, to keep compatability with DAGMC

Thanks 

Andy

Sent on a Sprint Samsung Galaxy Note® 3

-------- Original message --------
From: Anthony Scopatz notifications@github.com
Date:10/18/2014 2:23 PM (GMT-06:00)
To: pyne/pyne-ci pyne-ci@noreply.github.com
Cc:
Subject: Re: [pyne-ci] add python 3 build (#18)
Hopefully @gidden or @elliottbiondo, I don't plan on sleeping because of cyclus until the 24th :) — Reply to this email directly or view it on GitHub.
crbates commented 9 years ago

@makeclean I don't know enough about the MOAB development process to be comfortable committing to code thats still in RC status. Is 4.7.0RC1 considered production quality?

crbates commented 9 years ago

ping @gidden @elliottbiondo @scopatz

elliottbiondo commented 9 years ago

I will take a look at this tomorrow.

On Mon, Oct 27, 2014 at 11:44 PM, Cameron Bates notifications@github.com wrote:

ping @gidden https://github.com/gidden @elliottbiondo https://github.com/elliottbiondo @scopatz https://github.com/scopatz

— Reply to this email directly or view it on GitHub https://github.com/pyne/pyne-ci/pull/18#issuecomment-60709400.

scopatz commented 9 years ago

Hi @makeclean and @elliottbiondo and @julry, I think that you three are the only ones knowledgable enough about MOAB to make this change. Perhaps this should be a separate PR from one of you. In any event, MOAB versioning should not block python versioning. They are separate issues. Thanks!

elliottbiondo commented 9 years ago

The thinking was to start I would just add the Python3 build as a distinct platform build.

This seems fine to me.

In any event, MOAB versioning should not block python versioning.

Agreed. Merged.