Perhaps that warning at the end of my original email about __exit__ does
not matter, and I can just run ./configure now manually without any trouble?
------
Joseph Baker, PhD
Assistant Professor
Department of Chemistry
C101 Science Complex
The College of New Jersey
Ewing, NJ 08628
Phone: (609) 771-3173
Web: http://bakerj.pages.tcnj.edu/
On Fri, Apr 21, 2017 at 3:30 PM, Baker, Joseph <bakerj.tcnj.edu> wrote:
> Hi Hai,
>
> I just tried that and get the following output
>
> [root.neon amber16]# miniconda/bin/python update_amber --upgrade
> No major upgrade available.
> [root.neon amber16]#
>
>
> ------
> Joseph Baker, PhD
> Assistant Professor
> Department of Chemistry
> C101 Science Complex
> The College of New Jersey
> Ewing, NJ 08628
> Phone: (609) 771-3173
> Web: http://bakerj.pages.tcnj.edu/
>
>
> On Fri, Apr 21, 2017 at 3:27 PM, Nhai <nhai.qn.gmail.com> wrote:
>
> >
> >
> > > On Apr 21, 2017, at 3:23 PM, Baker, Joseph <bakerj.tcnj.edu> wrote:
> > >
> > > $AMBERHOME/miniconda/bin
> >
> > Uhm, python 2.6 does not have context manger for tarfile. Can you use
> > miniconda python
> >
> > $AMBERHOME/miniconda/bin/python update_amber --upgrade
> >
> > (Or use amber.python which is alias of miniconda python).
> >
> > Hai
> > _______________________________________________
> > AMBER mailing list
> > AMBER.ambermd.org
> > http://lists.ambermd.org/mailman/listinfo/amber
> >
> _______________________________________________
> AMBER mailing list
> AMBER.ambermd.org
> http://lists.ambermd.org/mailman/listinfo/amber
>
_______________________________________________
AMBER mailing list
AMBER.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber
Received on Fri Apr 21 2017 - 13:00:04 PDT
