imminent, either.
>
>> On Jun 7, 2017, at 3:08 PM, Michael J. Waters
>> wrote:
>>
>> Hi Daniel,
>>
>> So FiPy running in Python 3 won't have MPI based parallelism until
>> PyTrilinos supports Python 3?
>>
>> Best,
>>
>> -Mike
>
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 wrote:
>
> Hi Daniel,
>
> So FiPy running in Python 3 won't have MPI based parallelism until
> PyTrilinos support
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
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
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!
0xF0A5C638.asc
Description: application/pgp-keys
___
fipy mailing list
fipy@nist.gov
http://www.ctcms.nist.gov/fipy
As you say, there appears to be no sense of urgency in the Trilinos community
to make the upgrade. Unfortunate to say the least.
“…need to be on Python 3 for some reason”: I am evangelizing about Python to
students, postdocs, and senior colleagues, but I cannot in good conscience
recommend Py2
Since neither of the primary sparse solvers we use, PySparse or PyTrilinos, has
been migrated to Python 3, we're not in any rush.
FiPy can be used with Python 3 by running the `2to3` converter and then using
the SciPy sparse solvers. This doesn't perform as well, but is suitable if yo
Is there a timetable to migrate Fipy to Python 3?
Colin Stark
___
fipy mailing list
fipy@nist.gov
http://www.ctcms.nist.gov/fipy
[ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ]
Stefan,
I really appreciate the feedback. I have filed a ticket with the issues
that you've raised.
https://github.com/usnistgov/fipy/issues/432
Unfortunately, we are not giving FiPy the care it needs at the moment, but
hopefully we will have a coding spree before long and address some of these
l`, I still have/had some issues.
>>
>> For one, a few files have mixed indentation (mixed spaces
>> and tabs) which Python 3 doesn't like:
>>
>> Sorry: TabError: inconsistent use of tabs and spaces in indentation
>> (testBase.py, line 47)
>>
On Sun, Oct 19, 2014 at 4:57 PM, Stefan Schwarzer wrote:
>
>
> According to
>
> http://www.ctcms.nist.gov/fipy/documentation/USAGE.html#running-under-python-3
> you should also run `2to3 --write --doctests_only`. Maybe
> that makes the difference? :-)
>
Oh yeah. T
11 matches
Mail list logo
