Thanks for updating PyPI. Actually the svn reference was not a slip, I was following instructions on this page to install Fipy from source: http://matforge.org/fipy/wiki/InstallFiPy/MacOSX/SnowLeopard#FiPy which gives an "svn co" command. I missed the information on the main page about the git repository.
(But it should be noted that, when following the instructions on the page linked to, and using a source tarball from http://www.ctcms.nist.gov/fipy/download/, the installation process went smoothly.) Thanks again for the follow-up & links! Charles On Thu, Dec 12, 2013 at 7:05 AM, Guyer, Jonathan E. Dr. < jonathan.gu...@nist.gov> wrote: > On Dec 11, 2013, at 5:00 PM, Charles Reid <charlesre...@gmail.com> wrote: > > > Answered my own question - it looks like some modules went missing > between the 3.1 release tarball from the Fipy downloads page ( > http://www.ctcms.nist.gov/fipy/download/), which I was using, > > Actually, the issue is that PyPI never got updated. I've pushed version > 3.1 to PyPI and filed a ticket to correct our release procedures ( > http://matforge.org/fipy/ticket/661). Thanks for bringing this to our > attention. > > > > and the latest SVN version (which I assume is a better reflection of > what easy_install or pip use). > > As a point of clarification, in case this wasn't a slip of the tongue, we > no longer use SVN. We've been using Git for about a year and a half, so if > your source checkouts are from SVN, they're quite obsolete. See > http://www.ctcms.nist.gov/fipy/INSTALLATION.html#git-usage for more > information. > > > > _______________________________________________ > 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 ]
