Hi! My student, William Flynn, has been working a lot this summer using
sympy--thanks for all of the efforts on this project. We're doing some
work in a windows environment and find that pretty printing (to generate
pngs) still has a problem. Our hack at the moment is to use the python
subproce
I have written my own extensions to LatexPrinting (its parent class is
LatexPrinting) and it works fine, but is there a global way so that
print A
will actually execute
print latex(A)
so that I have to make fewer changes between terminal and latex printing
in the code.
--
You received this
Hi,
when I try something like :
>>> latex(1/x)
the answer is :
'${x}^{(-1)}$'
and not $\frac{1}{x}$.
Is it a way to get the previous result ? (I use sympy version :
0.5.8)
Thanks for any answer since my question is a newbies one !
--~--~-~--~~~---~--~--
print executes str(), so the only way to make print do that is to
override __str__. If you just want it for your own custom classes,
you can just override __str__ in those classes. Otherwise, you'll
have to hook Basic.__str__, as described at
http://docs.sympy.org/0.7.1/modules/printing.html.
Aa
On 04/17/2012 06:28 PM, Aaron Meurer wrote:
print executes str(), so the only way to make print do that is to
override __str__. If you just want it for your own custom classes,
you can just override __str__ in those classes. Otherwise, you'll
have to hook Basic.__str__, as described at
http://d
On Tue, Apr 17, 2012 at 4:41 PM, Alan Bromborsky wrote:
> On 04/17/2012 06:28 PM, Aaron Meurer wrote:
>>
>> print executes str(), so the only way to make print do that is to
>> override __str__. If you just want it for your own custom classes,
>> you can just override __str__ in those classes. O
On 04/17/2012 06:48 PM, Aaron Meurer wrote:
On Tue, Apr 17, 2012 at 4:41 PM, Alan Bromborsky wrote:
On 04/17/2012 06:28 PM, Aaron Meurer wrote:
print executes str(), so the only way to make print do that is to
override __str__. If you just want it for your own custom classes,
you can just ove
Ah, that's because Matrix doesn't subclass from Basic. You'll have to
hook it separately if you want it to work too.
By the way, forcing people to override Basic.__str__ is probably a bad
design. This was discussed a bit last summer with Gilbert's GSoC
project as I remember. Any thoughts on a bet
Thus -
Matrix.__str__ = lambda self: LatexPrinter().doprint(self)
allows me to print latex with the standard sympy LatexPrinter class with
a simple
print M
what is confusing me is that even though one creates a matrix with
Matrix(), I cannot find a matrix class in matrices.py or a
_print_
Matrix was renamed to MutableMatrix in a recent commit. The keyword
"Matrix" is now just an alias and rarely occurs in the low-level matrix
code.
Furthermore most MutableMatrix functions are actually defined on MatrixBase
which works for both Mutable and Immutable Matrices.
On Wed, Apr 18, 2012 a
Note that if you want to avoid the "Matrix is not Basic" issue and don't
mind immutability then you can use ImmutableMatrix instead.
On Wed, Apr 18, 2012 at 10:45 AM, Matthew Rocklin wrote:
> Matrix was renamed to MutableMatrix in a recent commit. The keyword
> "Matrix" is now just an alias and r
Am 18.04.2012 10:19, schrieb Aaron Meurer:
By the way, forcing people to override Basic.__str__ is probably a bad
design. This was discussed a bit last summer with Gilbert's GSoC
project as I remember. Any thoughts on a better way to do this?
Is there a writeup somewhere?
I wouldn't want to re
Le mercredi 18 avril 2012 à 02:19 -0600, Aaron Meurer a écrit :
> Ah, that's because Matrix doesn't subclass from Basic. You'll have to
> hook it separately if you want it to work too.
>
> By the way, forcing people to override Basic.__str__ is probably a bad
> design. This was discussed a bit la
Hi,
I have been toying around with the LaTeX printing over the last couple
of days and in the process have put together a few (potentially
idiosyncratic) changes to the printing class. I would be interested to
know what everyone thinks of this (i.e., is there enough interest that
it is wor
Hi all,
I have been toying around with a couple of ideas which might be worth
investigating for the LaTeX printer. First off, different bracket
styles depending on the nesting level. So it might go:
{ [ ( ( ) ) ] }; exactly how to do this I am unsure. It depends on how
easy it is to mainta
Hi all,
I have been looking at the printing of integrals in the LaTeX printer
and am interested in getting your opinions on the subject.
Firstly, we currently always print the 'd' (as in dx, dy, etc) in
italics. However, some books print it as a Roman (upright) character.
Mathematica prin
Sorry, this is a duplicate post if you follow the disussions on the google
codesite for this issue. I wanted to get as much input as possible.
Following a suggestion from Ondrej, I am replacing 'inline' = True or False
with 'mode' = 'inline', 'plain', 'equation' or 'equation*' for sympy.latex.
I n
I just posted this bug on github:
https://github.com/sympy/sympy/issues/8470
Here's a horrible example that shows what can happen
In [9]: latex(parse_expr("-B*A",evaluate=False))
Out[9]: 'A - B'
Fixing this problem is urgent for me. I have students entering answers like
this, and my website g
If you need your multiplication to be noncommutative you'll be better off
defining A and B to be commutative=False.
Aaron Meurer
On Tue, Nov 18, 2014 at 5:00 PM, Duane Nykamp wrote:
> I just posted this bug on github:
>
> https://github.com/sympy/sympy/issues/8470
>
> Here's a horrible example
No, I'm not worried about whether or not multiplication is commutative. I
just want to give feedback to the students that [[your answer]] is
(in)correct. I want [[your answer]] to be as close as possible to what
they type. I don't care if it changes the order of the factors. But, it's
bad i
a fix is in process at https://github.com/sympy/sympy/pull/8475
On Tuesday, November 18, 2014 5:52:13 PM UTC-6, Duane Nykamp wrote:
>
> No, I'm not worried about whether or not multiplication is commutative. I
> just want to give feedback to the students that [[your answer]] is
> (in)correct.
21 matches
Mail list logo