Hey Jon, No problem, instructions on wiki pages always have to be taken with a grain of salt. I'm happy to spend a little time updating the wiki instructions. Thanks for getting me set up with a matforge account!
Charles Charles On Wed, Dec 18, 2013 at 5:51 AM, Guyer, Jonathan E. Dr. < jonathan.gu...@nist.gov> wrote: > Charles, > > Thank you for bringing this to our attention. Those instruction wikis are > necessarily snapshots in time and it's very hard (pronounced "impossible") > to keep them up to date. I went to go fix the "svn co" for FiPy and > realized that the instructions for NumPy and SciPy also refer to svn and > that the whole page needed to be edited, which I didn't have time for. > > In that vein. It has just come to my attention that you have been waiting > for over a month to get a matforge account in order to contribute to our > wiki. This is absurd and you have my strongest apologies. I first learned > of this Monday evening and immediately said to approve it, but I learned > this morning that that still hasn't happened. I've just created your > account and will send you your initial password offline. I wish we didn't > require login at all, but we get overwhelmed with spam when we do that. > > - Jon > > On Dec 12, 2013, at 1:19 PM, Charles Reid <charlesre...@gmail.com> wrote: > > > 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 ] > > > _______________________________________________ > 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 ]
