Hi Niles,
On Wed, Sep 1, 2010 at 7:49 AM, Niles wrote:
> I've noticed a separate list of developers on the DevMap at
> sagemath.org . . . is there a plan to integrate these two lists?
There is a plan. Some people who are listed on the Dev Map are not
listed on the trac home page and vice versa,
On Aug 28, 1:21 pm, Sebastian Pancratz wrote:
> On Aug 27, 1:00 pm, luisfe wrote:
>
> > I have added a new ticket for adding a default gcd and lcm for field
> > elements.
>
> >http://trac.sagemath.org/sage_trac/ticket/9819
>
> > For the case of field elements gcd and lcm methods are not of grea
On Aug 31, 2010, at 8:15 PM, Ivan Andrus wrote:
> On Aug 31, 2010, at 7:37 PM, Jason Grout wrote:
>> When I click "stop server", and then "start server", I see this error
>> message in the log:
>>
>> Setting environment variables
>> Warning: Attempted to overwrite SAGE_ROOT environment variable
Does Sage have any sort of policy on using "pre-release" software in
.spkg files? By this I mean a package which is marked by the upstream
developers as a alpha/beta/release candiadate, or something someone
has grabbed by use of cvs/jit/svn etc.
I know this is sometimes happens - the Pari update i
As you will see from a previous email today, I'm not over-keen on the
use of unstable snapshots, but I'm aware they are sometimes necessary
http://www.sagemath.org/doc/developer/patching_spkgs.html#bumping-up-an-spkg-s-version
says "If the upstream package is taken from some revision other than a
Hi!
When I tried to create an spkg out of a folder with many uncommitted
changes in the mercurial repository, after a while the process hanged.
It was invisible to "top" and didn't finish (I waited something like
10 minutes). But after committing the changes, it worked fine and
quickly.
I doubt t
Hi!
The following happens with Sage-4.5.2
sage.math:
sage: L = [(360, {}), (2520, {0: 'X'}), ('prime', 3)]
sage: sorted(L)
[(360, {}), (2520, {0: 'X'}), ('prime', 3)]
bsd.math:
sage: L = [(360, {}), (2520, {0: 'X'}), ('prime', 3)]
sage: sorted(L)
[('prime', 3), (360, {}), (2520, {0:
Another issue,
Assuming that we allow a fallback implementation of gcd/lcm for field
elements.
Do we want such gcd/lcm if the field is non-exact?
FractionField(RR[x]) and so on.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email
On Sep 1, 6:58 am, Ivan Andrus wrote:
> On Aug 31, 2010, at 8:15 PM, Ivan Andrus wrote:
>
>
>
>
>
> > On Aug 31, 2010, at 7:37 PM, Jason Grout wrote:
> >> When I click "stop server", and then "start server", I see this error
> >> message in the log:
>
> >> Setting environment variables
> >> War
Any field with an is_zero() function on its elements is presumably OK?
John
On 1 September 2010 15:39, luisfe wrote:
> Another issue,
>
> Assuming that we allow a fallback implementation of gcd/lcm for field
> elements.
>
> Do we want such gcd/lcm if the field is non-exact?
>
> FractionField(RR[
On Sep 1, 2010, at 4:40 PM, kcrisman wrote:
> On Sep 1, 6:58 am, Ivan Andrus wrote:
>> On Aug 31, 2010, at 8:15 PM, Ivan Andrus wrote:
>>> On Aug 31, 2010, at 7:37 PM, Jason Grout wrote:
When I click "stop server", and then "start server", I see this error
message in the log:
>>
S
Dear Luis,
I think the points you raise are valid ones. Perhaps the following
would be a sensible solution?
Implement gcd and lcm for general field elements just as you suggest.
(So gcd(x,y) is 1 unless (x,y) is (0,0), in which case it is 0.) It
should be just fine for inexact fields, too, so l
Tim,
all screwing around aside for a moment. I broadly agree with your
sentiments. However, there are also some issues with what you are
suggesting. And I mean to make these observations in all seriousness.
One of the reasons we have been rewriting things like ZZ and ZZ[x] is
that there has been
Hi,
Expect downtime, instability, reboots, etc. Today on the sagemath
infrastructure.
William
--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an ema
Has anyone given thought for making Sage read Mathematica syntax? I've
seen a recent video from William stating it is NOT an aim of Sage to
be clone of any of the 4 M's - in contrast, Octave is a clone of
MATLAB.
Whilst parsing Mathematica code is not an aim of Sage, I doubt many
would are argue t
Hi there,
When I try to connect to trac I get the following:
Warning:
* Can't synchronize with the repository (/usr/local/sage/devel/sage does
not appear to contain a Mercurial repository.). Look in the Trac log for more
information.
* Can't synchronize with the repository (/usr
Hello everybody !!!
I've been writing a tutorial for LP, and I hope the Graph tutorial
will follow, but I have a problem with doctests... Something like that
:
sage: g = Graph()
Now we add a vertex ::
sage: g.add_vertex(1)
does not work as Sphinx forgets the definition of "g" between
d
(btw, this is ticket 9836)
Nathann
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sage
On 1 September 2010 17:16, Nathann Cohen wrote:
> Hello everybody !!!
>
> I've been writing a tutorial for LP
> Nathann
It would be good if you could update that bit of the documentation
that tells one how to load the optional GPLK package, when GLPK is now
a standard package. If you have not cr
On Sep 1, 5:27 pm, Sebastian Pancratz wrote:
> I don't think this change in code should be used as a band-aid to make
> things work in one of the trac tickets you mentioned earlier.
For the problem that raised all the stuff up I have an alternative
solution (with pros and cons of course)
> On
On Sep 1, 11:55 am, David Kirkby wrote:
> Has anyone given thought for making Sage read Mathematica syntax? I've
> seen a recent video from William stating it is NOT an aim of Sage to
> be clone of any of the 4 M's - in contrast, Octave is a clone of
> MATLAB.
>
> Whilst parsing Mathematica code
On 1 September 2010 17:45, kcrisman wrote:
>
>
> On Sep 1, 11:55 am, David Kirkby wrote:
>> Has anyone given thought for making Sage read Mathematica syntax? I've
>> seen a recent video from William stating it is NOT an aim of Sage to
>> be clone of any of the 4 M's - in contrast, Octave is a clo
On Sep 1, 9:21 am, Florent Hivert
wrote:
> Hi there,
>
> When I try to connect to trac I get the following:
>
> Warning:
>
> * Can't synchronize with the repository (/usr/local/sage/devel/sage does
> not appear to contain a Mercurial repository.). Look in the Trac log for more
> inf
On 1 September 2010 14:21, Florent Hivert wrote:
> Hi there,
>
> When I try to connect to trac I get the following:
>
> Warning:
>
> * Can't synchronize with the repository (/usr/local/sage/devel/sage does
> not appear to contain a Mercurial repository.). Look in the Trac log for more
>
On Wed, Sep 1, 2010 at 9:16 AM, Nathann Cohen wrote:
> Any idea how to fix it ?
You need to use ".. link" to connect a doctest block with the one
above it. For example,
{{{
.. link
::
sage: d.items()
[(1, 5), ('sage', 17), (Integer Ring, Finite Field of size 7)]
}}}
Look in the tutor
On Wed, Sep 1, 2010 at 7:23 AM, Simon King wrote:
> Any idea why sorted has become machine dependent?
It's always been somewhat machine dependent -- see
http://yz.mit.edu/wp/default-behavior-of-pythons-cmp/ .
--Mike
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsu
On Sep 1, 1:30 pm, David Kirkby wrote:
> On 1 September 2010 17:45, kcrisman wrote:
>
>
>
> > On Sep 1, 11:55 am, David Kirkby wrote:
> >> Has anyone given thought for making Sage read Mathematica syntax? I've
> >> seen a recent video from William stating it is NOT an aim of Sage to
> >> be cl
Hi Mike!
On 1 Sep., 19:45, Mike Hansen wrote:
> It's always been somewhat machine dependent --
> seehttp://yz.mit.edu/wp/default-behavior-of-pythons-cmp/.
Ah! So, the problem is that I have both strings and integers, there is
no __cmp__ implemented that compares both, and thus the two are
compa
On Wed, Sep 1, 2010 at 11:00 AM, Simon King wrote:
> But then, what can one do? I.e., how can one safely doctest the
> contents of a dictionary D?
You could build the dictionary and check that it is equal to the
dictionary in question:
sage: L
{360: {}, 2520: {0: 'X'}, 'prime': 3}
sage: dict([(3
Hi Mike!
On 1 Sep., 20:05, Mike Hansen wrote:
> You could build the dictionary and check that it is equal to the
> dictionary in question:
>
> sage: L
> {360: {}, 2520: {0: 'X'}, 'prime': 3}
> sage: dict([(360, {}), (2520, {0: 'X'}), ('prime', 3)]) == L
> True
Good idea!
Thank you,
Simon
--
T
On Sep 1, 11:00 am, Simon King wrote:
> But then, what can one do? I.e., how can one safely doctest the
> contents of a dictionary D?
If the default choice of "sorted" is not portable, make sure to tell
the system to sort on something that is portable, like you suggest:
> At least in this examp
Hello everyone,
This is a reminder that a patch for multivariate power series is
waiting for review at
http://trac.sagemath.org/sage_trac/ticket/1956
The idea is to implement multivariate power series as univariate power
series over a multivariate polynomial ring; the power series variable
is th
Hi,
Most sage.math related infrastructure will be down for the next few
hours for maintenance.
William
--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, se
Hello everyone,
Over at asksage, I complained that the sage documentation bears no
resemblance to sagemath.org, and I for one actually did find this a
little confusing at first (until I realized that all python
documentation looks like this, by default). That complaint got a
couple of up-votes, s
+1
On Wed, Sep 1, 2010 at 2:33 PM, Niles wrote:
> Hello everyone,
>
> Over at asksage, I complained that the sage documentation bears no
> resemblance to sagemath.org, and I for one actually did find this a
> little confusing at first (until I realized that all python
> documentation looks like t
On Wed, Sep 1, 2010 at 2:33 PM, Niles wrote:
> Hello everyone,
>
> Over at asksage, I complained that the sage documentation bears no
> resemblance to sagemath.org, and I for one actually did find this a
> little confusing at first (until I realized that all python
> documentation looks like this,
On Wed, Sep 1, 2010 at 6:03 PM, William Stein wrote:
> On Wed, Sep 1, 2010 at 2:33 PM, Niles wrote:
>> Hello everyone,
>>
>> Over at asksage, I complained that the sage documentation bears no
>> resemblance to sagemath.org, and I for one actually did find this a
>> little confusing at first (unti
On 09/01/2010 04:33 PM, Niles wrote:
> Over at asksage, I complained that the sage documentation bears no
> resemblance to sagemath.org, and I for one actually did find this a
> little confusing at first (until I realized that all python
> documentation looks like this, by default). That complaint
Looks good to me too. Nice idea.
Did you experiment with the background color on the verbatim stuff
(doctests)? Looks like strings print in blue, so that probably
wouldn't be a good choice and maybe there is enough blue already. The
sick green has always been a bit jarring to my eye. Maybe a l
On 09/ 1/10 02:19 AM, Alex Ghitza wrote:
On Wed, 01 Sep 2010 00:07:43 +0100, "Dr. David Kirkby"
wrote:
It's nice to know that running the tests 100 times and reporting the failures
managed to unearth a bug.
I'm not sure I would call this a bug, but it is definitely something
that's very easy
On 09/01/2010 07:43 AM, Simon King wrote:
> When I tried to create an spkg out of a folder with many uncommitted
> changes in the mercurial repository, after a while the process hanged.
> It was invisible to "top" and didn't finish (I waited something like
> 10 minutes). But after committing the ch
Hi,
1. sagenb.org, sagemath.org, sage.math, boxen.math, etc., should all
be back up.
2. I rebooted boxen, mod, and geom after upgrading their "ILOM
Firmware", so if you had jobs running on any of those machines, they
were killed.
3. The computer "disk.math" serves everybody's home directories; i
Here's an interesting talk by Thomas Wouters on "Advanced Python (or
understanding Python)"
http://www.youtube.com/watch?v=E_kZDvwofHY
It's a few years old, but it could still be useful to intermediate
Python programmers.
--
To post to this group, send an email to sage-devel@googlegroups.com
To
For A and B Parents, should A == B ever differ from A is B? This came up in
tracking down a p-adics bug, but there's at least one place that assumes the
equivalence of these conditions. The place I'm thinking of is in
sage.categories.hom_set.Hom, where it checks a cache to see if the Homset
has b
On 9/1/10 10:32 AM, Bill Hart wrote:
Tim,
all screwing around aside for a moment. I broadly agree with your
sentiments. However, there are also some issues with what you are
suggesting. And I mean to make these observations in all seriousness.
I'm reading this thread with great interest. Tho
On 9/1/10 7:00 AM, David Kirkby wrote:
Should any desire to update to a non-stable release be discussed on
sage-devel first?
That sounds reasonable to me.
Jason
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-dev
On 9/1/10 5:17 PM, Rob Beezer wrote:
Looks good to me too. Nice idea.
Did you experiment with the background color on the verbatim stuff
(doctests)? Looks like strings print in blue, so that probably
wouldn't be a good choice and maybe there is enough blue already. The
sick green has always b
On 9/1/10 7:25 PM, David Roe wrote:
P.S. To find an example of two parents which currently compare as equal but
are not the same object, do
sage: R = Zp(5, print_sep="|")
sage: S = Zp(5, print_sep=":")
sage: R == S
True
sage: R is S
False
Carl Witty commented on a similar issue in printing i
> > > 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
Hi there,
On Wed, Sep 01, 2010 at 08:27:22PM -0500, Jason Grout wrote:
> On 9/1/10 7:25 PM, David Roe wrote:
>
> >P.S. To find an example of two parents which currently compare as equal but
> >are not the same object, do
> >sage: R = Zp(5, print_sep="|")
> >sage: S = Zp(5, print_sep=":")
>
On 2 September 2010 04:01, Felix Lawrence wrote:
> I think there's some confusion here. kcrisman seems to be talking
> about allowing the Mathematica interface to parse mathematica output,
> importing it to Sage. Dave seems to be proposing writing something
> that lets Sage run mathematica code
On 2 September 2010 02:12, Jason Grout wrote:
> On 9/1/10 7:00 AM, David Kirkby wrote:
>
>> Should any desire to update to a non-stable release be discussed on
>> sage-devel first?
>
>
> That sounds reasonable to me.
>
> Jason
Thank you Jason.
Who would agree with making this a policy and so add
> On 2 September 2010 02:12, Jason Grout wrote:
> > On 9/1/10 7:00 AM, David Kirkby wrote:
> >> Should any desire to update to a non-stable release be discussed on
> >> sage-devel first?
> >
> > That sounds reasonable to me.
> >
> > Jason
>
> Thank you Jason.
>
> Who would agree with making th
the mathematica syntax parser that I wrote appears to run inside
Maxima, so
you can, if you wish, feed such text to the mma-in-maxima system.
The intent in that project is mainly to take mma syntax for
expressions and map it into
maxima, and not take the big step of having a more-or-less full
ma
On 2 Sep, 05:55, François Bissey wrote:
> > Who would agree with making this a policy and so adding to the Sage
> > Developers Guide a few sentences saying that any updates of packages
> > that are not to a stable release (i.e snapshots, alpha, beta, release
> > candidates etc) should be discu
> On 2 Sep, 05:55, François Bissey wrote:
> > > Who would agree with making this a policy and so adding to the Sage
> > > Developers Guide a few sentences saying that any updates of packages
> > > that are not to a stable release (i.e snapshots, alpha, beta, release
> > > candidates etc) should b
56 matches
Mail list logo
