Hi,
> To avoid spending time on debug different Python distributions, we just
> force user to use Miniconda (much lighter than Anaconda) as we ...
This seems to be a different standard than we apply to other source
languages; for example, we do not force gnu compilers, but rather
support several vendors. And we try to advance to the next official
language standards only when all or most vendors support that standard.
scott
On Wed, Dec 21, 2016 at 11:45:10AM -0500, Hai Nguyen wrote:
> 1. I absolutely agree that the message is vague. I made change to the
> current behavior without update the message.
> We (Dave, me and Scott) had very long discussion about checking Python.
> However, Dave and I have the same consensus that the checking is not always
> reliable, especially user uses system Python (e.g on Mac).
> To avoid spending time on debug different Python distributions, we just
> force user to use Miniconda (much lighter than Anaconda) as we (me, Dave,
> Jason, ...) use it in production.
>
> So I think the configure2 should exit you user saying "N" to force him/her
> to use --with-python or --skip-python flag.
>
> If you have different amber dirs, just simply
>
> bash configure --with-python=$HOME/anaconda/bin/python gnu
>
...
>
> On Wed, Dec 21, 2016 at 11:12 AM, Daniel Roe <daniel.r.roe.gmail.com> wrote:
...
> I think, 'configure' needs to 1) check that the
> > current python installation will work, 2) if it won't work, tell me
> > exactly why, and what I might do to make my python install
> > Amber-compatible (what packages etc), and 3) if certain python
> > components are going to be skipped and others not, tell me up-front
> > which ones.
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Wed Dec 21 2016 - 09:30:03 PST
