Yes. More likely to happen is that we'll add support for PETSc, but that's not imminent, either.
> On Jun 7, 2017, at 3:08 PM, Michael J. Waters <waters.mik...@gmail.com> wrote: > > Hi Daniel, > > So FiPy running in Python 3 won't have MPI based parallelism until > PyTrilinos supports Python 3? > > Best, > > -Mike > > > On 6/7/17 2:01 PM, Daniel Wheeler wrote: >> Hi Nils, >> >> FiPy is not written for Python 3, but it does work after applying >> 2to3. However, only the Scipy solvers are then available. See, >> >> >> https://www.ctcms.nist.gov/fipy/documentation/USAGE.html#running-under-python-3 >> >> To fully make the switch to Python 3, FiPy needs to be natively >> updated, which hasn't happened yet. Also, FiPy needs to move away from >> using Trilinos as PyTrilinos hasn't been updated to Python 3. >> Unfortunately, I can't give a timeline on when those changes will be >> made. >> >> Cheers, >> >> Daniel >> >> >> >> >> On Wed, Jun 7, 2017 at 6:16 AM, Nils Becker >> <nils.bec...@bioquant.uni-heidelberg.de> wrote: >>> hi, >>> >>> i'm considering updating my scripts from 2.7 to python 3.4 or 3.6. >>> should i expect any problems? is fipy tested on py 3? >>> >>> thanks! >>> >>> _______________________________________________ >>> fipy mailing list >>> fipy@nist.gov >>> http://www.ctcms.nist.gov/fipy >>> [ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ] >>> >> >> > > _______________________________________________ > fipy mailing list > fipy@nist.gov > http://www.ctcms.nist.gov/fipy > [ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ] _______________________________________________ fipy mailing list fipy@nist.gov http://www.ctcms.nist.gov/fipy [ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ]
