#15261: Fix brian optional spkg for new workflow
--------------------------------------+-------------------------
Reporter: kcrisman | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-5.13
Component: packages: optional | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
--------------------------------------+-------------------------
Old description:
> See #14962. We have to either fix the newest version checking in brian
> or (better) get rid of it completely.
>
> This would be an ideal time to upgrade brian to a new version and use the
> patch file instead of the py file for the one fix that is in it.
New description:
See #14962. We have to either fix the newest version checking in brian or
(better) get rid of it completely.
This would be an ideal time to upgrade brian to a new version and use the
patch file instead of the py file for the one fix that is in it.
I have two different spkgs to try.
* http://sage.math.washington.edu/home/kcrisman/brian-1.2.1.p1.spkg
* http://sage.math.washington.edu/home/kcrisman/brian-1.4.1.p0.spkg
--
Comment (by kcrisman):
I have two different ones to try. I think I got the patches right for the
upgrade. Oriol, can you check that this still works for your clash issue
with Sage-defined types?
--
Ticket URL: <http://trac.sagemath.org/ticket/15261#comment:3>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/groups/opt_out.
