On Tue, May 19, 2009 at 12:18 PM, Brian Grangerellisonbg@gmail.com wrote:
I agree that there still is a problem. Before, I didn't think that
Sage's matplotlib would need to have different options to even be able
to function.
The problem that I am running into is that my
I want to reopen this thread.
Great! matplotlib under Sage is still broken for me because of this
issue - I would love to see this resolved.
I have a build farm with many (nearly 20) different OS's that all build and
test
Sage in parallel. My home directory on each of those machines is
2009/6/6 Brian Granger ellisonbg@gmail.com:
I want to reopen this thread.
Great! matplotlib under Sage is still broken for me because of this
issue - I would love to see this resolved.
I have a build farm with many (nearly 20) different OS's that all build and
test
Sage in
But, wait, does SAGE_HOME point to $HOME/.sage by default? That is
the right place for this, I just don't remember exactly where
SAGE_HOME points.
Yep, it does. We can make sure easily enough by running Sage and asking:
sage: DOT_SAGE
'/Users/wstein/.sage/'
By the way, I just realized
Brian Granger wrote:
I want to reopen this thread.
Great! matplotlib under Sage is still broken for me because of this
issue - I would love to see this resolved.
I have a build farm with many (nearly 20) different OS's that all build and
test
Sage in parallel. My home directory on
William Stein wrote:
4. Do export MPLCONFIGDIR=$DOT_SAGE/matplotlibconfig
That avoids every single problem above. :-)
Brilliant. It does leave an unused and possibly confusing matplotlibrc
file in their .sage directory, but I suppose that's happening right now,
so it's not any worse
This sounds great. However, what do we do about every sage install that
exists out there right now? Every .sage directory already has a
matplotlibrc file that throws warnings with the current matplotlibrc.
Back when the decision was made, some ideas were kicked around:
1. Make a FAQ entry
Brian Granger wrote:
This sounds great. However, what do we do about every sage install that
exists out there right now? Every .sage directory already has a
matplotlibrc file that throws warnings with the current matplotlibrc.
Back when the decision was made, some ideas were kicked around:
ah, right, I wasn't understanding your solution (for some reason, I
thought you were using what we used before, not a new variable pointing
to a new directory).
+1 to your solution (I'd rather use your more standard directory name
over William's non-standard name).
It is important to set
I agree that there still is a problem. Before, I didn't think that
Sage's matplotlib would need to have different options to even be able
to function.
The problem that I am running into is that my
~./matplotlib/matplotlibrc sets a backend (macosx) that the Sage
matplotlib doesn't have.
On Mon, May 18, 2009 at 2:51 PM, Brian Granger ellisonbg@gmail.com wrote:
Currently:
IF a user has matplotlib installed outside of Sage
AND they have a matplotlibrc file in ~/.matplotlib
THEN Sage will use the non-Sage version in ~/.matplotlib/matplotlibrc.
If a user has set a
True, we fixed this in SPD because it is a problem there, however, I
also have this problem with Sage. I download Sage, install it, and it
doesn't work (because I have a .matplotlib/matplotlibrc file).
I will look around for previous posts on this though.
Brian
On Mon, May 18, 2009 at 2:58
Brian Granger wrote:
True, we fixed this in SPD because it is a problem there, however, I
also have this problem with Sage. I download Sage, install it, and it
doesn't work (because I have a .matplotlib/matplotlibrc file).
I will look around for previous posts on this though.
Details
Hi Brian,
no need to CC me on bug reports you send to sage-devel.
Cheers,
Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For
Well I don't like it. So it sounds like a bug to me.
OK thanks. Could you or someone with a Sage Trac account create a
ticket for this? Oh, and Ondrej tried this on Linux but did not see
this bug.
Cheers,
Brian
--~--~-~--~~~---~--~~
To post to this group,
OK
On Mon, May 18, 2009 at 3:31 PM, Michael Abshoff
mabsh...@googlemail.com wrote:
Hi Brian,
no need to CC me on bug reports you send to sage-devel.
Cheers,
Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
Details are here: http://trac.sagemath.org/sage_trac/ticket/4774
I have skimmed though this as well as the previous thread on this
topic. But, it still seems like the original problem remains (Sage's
matplotlib using the wrong matplotlibrc) even though Sage no longer
includes its own
Brian Granger wrote:
Details are here: http://trac.sagemath.org/sage_trac/ticket/4774
I have skimmed though this as well as the previous thread on this
topic. But, it still seems like the original problem remains (Sage's
matplotlib using the wrong matplotlibrc) even though Sage no longer
On Aug 27, 2008, at 1:54 PM, David Ketcheson wrote:
Thanks for the nice fix. I've managed to break things in a new way:
sage: from sympy import Symbol
sage: x,y=Symbol('x',False),Symbol('y',False)
sage: 1/2+y*x
x*y + 1/2
sage: y*x+1/2
1/2 + y*x
The 'False' argument to Symbol here
On Thu, Aug 28, 2008 at 9:54 AM, Robert Bradshaw
[EMAIL PROTECTED] wrote:
On Aug 27, 2008, at 1:54 PM, David Ketcheson wrote:
Thanks for the nice fix. I've managed to break things in a new way:
sage: from sympy import Symbol
sage: x,y=Symbol('x',False),Symbol('y',False)
sage: 1/2+y*x
For now I have resorted to simply manipulating strings for what I
want, which is simply to be able to do symbolic algebra with matrices
and vectors. I may be interested in developing this functionality
myself for Sage. What is the plan for symbolic algebra in sage? Will
'var's eventually do
On Wed, Aug 27, 2008 at 10:54 PM, David Ketcheson [EMAIL PROTECTED] wrote:
Thanks for the nice fix. I've managed to break things in a new way:
sage: from sympy import Symbol
sage: x,y=Symbol('x',False),Symbol('y',False)
sage: 1/2+y*x
x*y + 1/2
sage: y*x+1/2
1/2 + y*x
The 'False'
On Thu, Aug 28, 2008 at 11:04 AM, David Ketcheson [EMAIL PROTECTED] wrote:
For now I have resorted to simply manipulating strings for what I
want, which is simply to be able to do symbolic algebra with matrices
and vectors. I may be interested in developing this functionality
myself for
So I'd suggest:
- to open a trac ticket for the particular issue you have (if you don't
have a Trac account yet, I can do that for you)
A patch is up for review (hint, hint) at:
http://trac.sagemath.org/sage_trac/ticket/3892
Cheers,
Martin
--
name: Martin Albrecht
_pgp:
Thanks for the nice fix. I've managed to break things in a new way:
sage: from sympy import Symbol
sage: x,y=Symbol('x',False),Symbol('y',False)
sage: 1/2+y*x
x*y + 1/2
sage: y*x+1/2
1/2 + y*x
The 'False' argument to Symbol here means the symbols are non-
commutative. Adding a rational
Hi David,
That's the bug; if anyone knows of a workaround for now I'd like to
hear it. My code builds up complicated expressions involving
rationals and symbols, and no matter how I reorder things, one of them
fails in this manner. I know I can use 'var' instead of 'Symbol', but
I need
On Monday 18 August 2008, Hamish Ivey-Law wrote:
Hello,
I found a bug that occurs when calling random_element() on a
polynomial or power series ring over a Givaro finite field (the Givaro
finite fields are used when the field is non-prime and has cardinality
2^16). The problem is that
On Aug 18, 4:31 pm, Martin Albrecht [EMAIL PROTECTED]
wrote:
On Monday 18 August 2008, Hamish Ivey-Law wrote:
Hello,
I found a bug that occurs when calling random_element() on a
polynomial or power series ring over a Givaro finite field (the Givaro
finite fields are used when the
So I'd suggest:
- to open a trac ticket for the particular issue you have (if you don't
have a Trac account yet, I can do that for you)
I don't have a Trac account yet, so that would be good, thanks.
This is now
http://trac.sagemath.org/sage_trac/ticket/3892
- we open another
Hi, I don't have time to debug this now, but I want to mention that
it sounds suspiciously similar to this ticket:
http://sagetrac.org/sage_trac/ticket/2943
Maybe there are some clues there, but I never quite got to the bottom
of it.
david
On Jul 17, 2008, at 8:50 AM, Hamish wrote:
Dear
On Jul 17, 2:58 pm, David Harvey [EMAIL PROTECTED] wrote:
I don't have time to debug this now, but I want to mention that
it sounds suspiciously similar to this ticket:
http://sagetrac.org/sage_trac/ticket/2943
It certainly does. (I probably should have filtered the tickets with
power
On Jul 17, 2008, at 9:51 AM, Hamish wrote:
I don't have time to debug this now, but I want to mention that
it sounds suspiciously similar to this ticket:
http://sagetrac.org/sage_trac/ticket/2943
It certainly does. (I probably should have filtered the tickets with
power series instead of
On Tue, Jun 10, 2008 at 11:04 PM, mabshoff [EMAIL PROTECTED] wrote:
Riccardo Gori wrote:
Hello,
Hi Riccardo,
thanks for the bug report. I have forwarded it to sage-devel.
Cheers,
Michael
In SAGE-3.0.2 with a Intel Mac OSX 10.5 I found the following bug:
Trying to evaluate a sympy
On Wed, Jun 11, 2008 at 2:32 AM, mabshoff [EMAIL PROTECTED] wrote:
On Jun 10, 5:27 pm, William Stein [EMAIL PROTECTED] wrote:
On Tue, Jun 10, 2008 at 2:04 PM, mabshoff [EMAIL PROTECTED] wrote:
Riccardo Gori wrote:
Hello,
Hi Riccardo,
I have also forwarded your email to sage-devel.
On Wed, Jun 11, 2008 at 11:32 AM, Ondrej Certik [EMAIL PROTECTED] wrote:
On Tue, Jun 10, 2008 at 11:04 PM, mabshoff [EMAIL PROTECTED] wrote:
Riccardo Gori wrote:
Hello,
Hi Riccardo,
thanks for the bug report. I have forwarded it to sage-devel.
Cheers,
Michael
In SAGE-3.0.2 with a
On Wed, Jun 11, 2008 at 2:46 AM, Ondrej Certik [EMAIL PROTECTED] wrote:
On Wed, Jun 11, 2008 at 2:32 AM, mabshoff [EMAIL PROTECTED] wrote:
On Jun 10, 5:27 pm, William Stein [EMAIL PROTECTED] wrote:
On Tue, Jun 10, 2008 at 2:04 PM, mabshoff [EMAIL PROTECTED] wrote:
Riccardo Gori wrote:
On Wed, Jun 11, 2008 at 2:56 PM, William Stein [EMAIL PROTECTED] wrote:
On Wed, Jun 11, 2008 at 2:46 AM, Ondrej Certik [EMAIL PROTECTED] wrote:
On Wed, Jun 11, 2008 at 2:32 AM, mabshoff [EMAIL PROTECTED] wrote:
On Jun 10, 5:27 pm, William Stein [EMAIL PROTECTED] wrote:
On Tue, Jun 10,
On Wed, Jun 11, 2008 at 1:08 PM, Ondrej Certik [EMAIL PROTECTED] wrote:
On Wed, Jun 11, 2008 at 11:32 AM, Ondrej Certik [EMAIL PROTECTED] wrote:
On Tue, Jun 10, 2008 at 11:04 PM, mabshoff [EMAIL PROTECTED] wrote:
Riccardo Gori wrote:
Hello,
Hi Riccardo,
thanks for the bug report. I have
On Wed, Jun 11, 2008 at 3:16 PM, Ondrej Certik [EMAIL PROTECTED] wrote:
On Wed, Jun 11, 2008 at 2:56 PM, William Stein [EMAIL PROTECTED] wrote:
On Wed, Jun 11, 2008 at 2:46 AM, Ondrej Certik [EMAIL PROTECTED] wrote:
On Wed, Jun 11, 2008 at 2:32 AM, mabshoff [EMAIL PROTECTED] wrote:
On
Riccardo Gori wrote:
Hello,
Hi Riccardo,
I have also forwarded your email to sage-devel.
In SAGE-3.0.2 with a Intel Mac OSX 10.5 I found the following bug:
If I create a sympy matrix and if I try to access it it gives me an error.
Step to reproduce:
sage: import sympy
sage: M =
Riccardo Gori wrote:
Hello,
Hi Riccardo,
thanks for the bug report. I have forwarded it to sage-devel.
Cheers,
Michael
In SAGE-3.0.2 with a Intel Mac OSX 10.5 I found the following bug:
Trying to evaluate a sympy function gives a wrong result. With sympy in a
python shell everything
On Tue, Jun 10, 2008 at 2:04 PM, mabshoff [EMAIL PROTECTED] wrote:
Riccardo Gori wrote:
Hello,
Hi Riccardo,
I have also forwarded your email to sage-devel.
In SAGE-3.0.2 with a Intel Mac OSX 10.5 I found the following bug:
If I create a sympy matrix and if I try to access it it gives
On Jun 10, 5:27 pm, William Stein [EMAIL PROTECTED] wrote:
On Tue, Jun 10, 2008 at 2:04 PM, mabshoff [EMAIL PROTECTED] wrote:
Riccardo Gori wrote:
Hello,
Hi Riccardo,
I have also forwarded your email to sage-devel.
In SAGE-3.0.2 with a Intel Mac OSX 10.5 I found the following
On Fri, 06 Jun 2008 at 09:40PM +0200, Michael Abshoff wrote:
종현 정 wrote:
- The direction field graph doesn't change the angle of arrows when
the aspect ratio, that is, the ratio of x's unit length and y's unit
length changes. The blue line and the field vectors should have the
same
종현 정 wrote:
Dear Jong Hyun Jung,
Dear whom it may concern,
I am writing about a bug report on plot_vector_field.
**
* OS Name: Microsoft Windows XP Home Edition
o Version: 5.1.2600 Service Pack 2 Build 2600
o Processor: x86 Family 6 Model
On Thu, 6 Mar 2008 12:53:43 -0800 (PST)
VictorMiller [EMAIL PROTECTED] wrote:
The following code causes a crash:
R = BooleanPolynomialRing(2)
f = 1 + R.gens()[0]
s = f.set()
t = set(s)
# this happened on sagenb.org, as well as the latest SAGE version
installed locally.
This is a
46 matches
Mail list logo
