On Sun, Nov 2, 2014 at 2:00 PM, Stefan Schwarzer <[email protected]> wrote:
> Hi Daniel, > > On 2014-11-02 19:39, Stefan Schwarzer wrote: > >> There are certianly some rough edges with FiPy and > >> Python 3 that we need to address. > > > > The first thing I'd like to see > > Oops. What I wanted to say: The first thing I'd like to see > is to be able to install FiPy directly from PyPI in a plain > virtualenv. That would already remove quite a few hurdles. > We should set that up so it is pip installable out of the box with Python 3 and also a conda recipe. It's in the issue tracker. > I suppose many people will try the installation, see some > `SyntaxError` (as I did) and assume Python 3 isn't supported > at all. `INSTALLATION.txt` seems to indicate the same, as > the information on Python 3 support is kind of "hidden" in > `documentation/USAGE.txt`. > Also added this to the issue. > You can also find a few tips on the common source code > approach in my talk from EuroPython 2014: > http://www.youtube.com/watch?v=9vNr_ZzZZAk > http://sschwarzer.com/download/python_2_3_europython2014.pdf > :-) > Thanks for that. That's very helpful. Thanks for picking through FiPy and pointing out the Python 3 issues. We'll hopefully get them ironed out. -- Daniel Wheeler
_______________________________________________ fipy mailing list [email protected] http://www.ctcms.nist.gov/fipy [ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ]
