Looking at the source for attached_files(), I don't see how removing
elements from the list it returns could detach the files. It looks
like you can detach files manually by deleting from the
sage.misc.preparser.attached dictionary, but there is a function
`detach` that does the job (as
On Apr 6, 7:19 pm, Dr. David Kirkby david.kir...@onetel.net wrote:
There seems to be a growing body of opinion that Clang
http://clang.llvm.org/
will replace gcc as the compiler of choice for open-source projects - not just
on OS X.
I've heard this too.
I also noticed that Xcode is no
I've just discovered a confidence-shattering bug with numpy matrices.
sage: mymat = numpy.matrix(numpy.arange(6).reshape(3,2))
sage: mymat[:,0]
matrix([[0, 2, 4]])
sage: mymat[:,int(0)]
matrix([[0],
[2],
[4]])
This caused the value of expressions to change when placed inside a
On Mar 5, 1:05 am, David Kirkby david.kir...@onetel.net wrote:
* I don't know of any way to add a finite element front end onto Sage,
but if there was, that would open up a huge range of possibilies.
There are some finite element software based on Python - see for
Should conversion from numpy arrays/matrices to lists and sage vectors/
matrices be implemented by a .sage() method on the numpy array/
matrix? This is more consistent with the behaviour interface objects.
diagonal_matrix(), matrix(), etc could then outsource the conversion
steps to .sage(),
On Dec 10, 10:09 am, William Stein wst...@gmail.com wrote:
A.H seems arbitrary? Why H?
I learnt linear algebra with A^H notation, with H denoting the
Hermitian transpose. Wikipedia lists the various names for the
conjugate transpose as conjugate transpose, Hermitian transpose,
Hermitian
whuss at some point added something like this for both Mma and Maple,
though very basic, as part of another ticket (symbolic sums?). I
can't remember where it is and am unfortunately having some internet
issues :( but anyway I believe this code was merged into Sage at some
point.
I'll take this opportunity to point out that the mathematica interface
is somewhat broken at present (i.e. calling .sage() on many
mathematica objects will cause an error, where previously it would
not). Ticket 8495 has a patch awaiting review that fixes this and
extends .sage() to work for many
I've put a patch up for http://trac.sagemath.org/sage_trac/ticket/8495
that fixes the regressions while keeping the new functionality:
sage -t -optional devel/sage/sage/interfaces/mathematica.py
[7.0 s]
--
All tests
On Mar 13, 2:41 am, Dr. David Kirkby david.kir...@onetel.net
wrote:
Felix Lawrence wrote:
But I've just noticed that mathematica doesn't seem to be responsible
for the weird orderings here after all - it seems to be sage itself.
For example:
sage: 4+I
I + 4
As Nick wrote some time ago
On Mar 12, 3:17 pm, Jason Grout jason-s...@creativetrax.com wrote:
So the Mathematica *input* syntax is closer to the sage *input* syntax,
while the mathematica full form (i.e., the internal tree of operations)
is closer to the sage tree of operations. That makes a lot of sense.
For
FullForm looks like a bit of a headache to me - in part one of the
examples given, InputForm gives Sqrt[5], whereas FullForm gives
Power[5,Rational[-1,2]]. The former is closer to sage's syntax and
should be easier to parse (and a basic parser for InputForm already
exists, in _sage_repr().) So
Grout jason-s...@creativetrax.com wrote:
On 03/10/2010 12:36 AM, Felix Lawrence wrote:
Hi David,
I haven't looked into these since #3587 rewrote
MathematicaElement._sage_() for mathematica objects, but I did a bit
of work getting the generic ExpectElement._sage_() to work
Hi David,
I haven't looked into these since #3587 rewrote
MathematicaElement._sage_() for mathematica objects, but I did a bit
of work getting the generic ExpectElement._sage_() to work with
mathematica lists. Mathematica does return different results
depending on whether it's running in 32-bit
Now that dsage has been laid to rest, http://sagemath.org/tour-research.html
should be updated as it still advertises dsage to be one of the top 5
sage features for researchers! Perhaps it could be replaced by a few
words about @parallel, which is still parallel computing (albeit not
Hi Minh,
The doctest failures in
sage -t -long devel/sage/sage/interfaces/expect.py
sage -t -long devel/sage/sage/interfaces/gp.py
are my fault - I forgot to include a 32-bit answer as well as the 64-
bit answer, e.g.
sage: gp(10.^80)._sage_repr()
On Sep 23, 12:58 pm, Minh Nguyen nguyenmi...@gmail.com wrote:
Hi Felix,
On Wed, Sep 23, 2009 at 12:10 PM, Felix Lawrence
fe...@physics.usyd.edu.au wrote:
Hi Minh,
The doctest failures in
sage -t -long devel/sage/sage/interfaces/expect.py
sage -t -long devel/sage
17 matches
Mail list logo