On Mon, Nov 17, 2014 at 10:53 AM, William Stein wst...@gmail.com wrote:
On Nov 17, 2014 10:42 AM, kcrisman kcris...@gmail.com wrote:
Is there a reason we need to have our own version?
Actually, I think there is, because see the original ticket #9675:
I must say I detected some problems
I guess it's not quite that bad. The fix was perhaps hackish.
sage: import brian
/Users/.../sage/local/lib/python2.7/site-packages/brian/utils/sparse_patch/__init__.py:39:
UserWarning: Couldn't find matching sparse matrix patch for scipy version
0.14.0, but in most cases this shouldn't be a
sage: !sage -i brian
Found package brian in
/usr/local/sage/sage-6.4/upstream/brian-1.4.1.p0.spkg
brian-1.4.1.p0
(Stripping trailing CRs from patch; use --binary to disable.)
patching file brian/units.py
Hunk #1 FAILED at 11173 (different line endings).
1 out of 1 hunk FAILED --
Is there a reason we need to have our own version?
Actually, I think there is, because see the original ticket #9675:
I must say I detected some problems with Brian units related to the Sage
classes 'RealNumber? http://trac.sagemath.org/wiki/RealNumber' and
'Integer', so I created a
On Nov 17, 2014 10:42 AM, kcrisman kcris...@gmail.com wrote:
Is there a reason we need to have our own version?
Actually, I think there is, because see the original ticket #9675:
I must say I detected some problems with Brian units related to the Sage
classes 'RealNumber?' and 'Integer',
On Sat, Nov 15, 2014 at 9:49 AM, William Stein wst...@gmail.com wrote:
Installing the brian optional package via sage -i brian seems broken
in Sage-6.4:
I think the solution should be to remove brian as a Sage optional
package, since one can just as well do
sage: !pip install brian
and that
The reason for the failure is that we updated patch and it is now less
lenient with malformed patches.
On Saturday, November 15, 2014 5:49:50 PM UTC, William wrote:
Installing the brian optional package via sage -i brian seems broken
in Sage-6.4:
sage: !sage -i brian
Found package
