Is there anyone that can provide me access to a OS X machine which defaults to
building 32-bit executable, but can build 64-bit executables? Ideally a machine
that has been used to compile 64-bit executables of Sage.
There's a lot of code in Sage which has something like this in it:
if [ `unam
Hi all,
So we're currently working on a long-overdue release of Cython with
all kinds of snazzy new features. However, our automated testing
system seems to keep turning up sporadic segfaults when running the
sage doctest suite. This is obviously bad, but we're having a hard
time reproducing this
Hi, I think both the links are pointing to the same patch, which I've
been working on recently--thanks for taking a look! To get the patch
from trac to work, I think you need to use mercurial; there are some
instructions in the sage developer guide, but in case you don't feel
like going through al
On Wed, Jul 28, 2010 at 11:55 AM, kcrisman wrote:
> Dear all,
>
> I recently got back from useR! 2010, the R user conference. This was
> the second time the conference was held in the US, this time at NIST
> (a government agency in suburban DC).
>
> The most important thing for Sage folks is prob
On Thu, Jul 29, 2010 at 10:25 AM, Sergey Bochkanov
wrote:
> Hello, Carl.
>
> Here is some documentation about Python-ALGLIB interface (called
> X-interface in this document):
>
> http://www.alglib.net/share/2010-07-26-alglib-for-sage/x-interface.pdf
Thanks.
> It is very short, but shoul
Hi!
On 30 Jul., 01:03, Bill Hart wrote:
> The original Sage code from the googlegroups/trac message you link to
> doesn't seem to work in current sage any more. I couldn't find a
> multivariable power series ring in the reference manual either, but
> may not have been looking hard enough.
I thin
The original Sage code from the googlegroups/trac message you link to
doesn't seem to work in current sage any more. I couldn't find a
multivariable power series ring in the reference manual either, but
may not have been looking hard enough.
Doing these computations in Sage generically, seems to t
On 07/29/2010 11:19 AM, kcrisman wrote:
> That is, without setting NUM_THREADS or something. I tried
>
> ./sage -testall -p 8
>
> but I just get lots of error messages in addition to my test output.
> I guess I have the same question about sage -tnew as well.
The 'sage -testall' and 'sage -tnew
sorry, wrong list.
Am 30.07.2010 00:01, schrieb Johannes:
> Hi list,
> i try to solve a linear equation in ZZ in the variables w_i:
>
> sage: variables = [var("w" + str(i),domain=ZZ)for i in range(s.nvertices())]
> sage: eq
> (w0 + w1 + w2 - 14*w3, w1 + 2*w2 - 8*w3, 2*w2 - 3*w3)
> sage: result
> [w
Hi list,
i try to solve a linear equation in ZZ in the variables w_i:
sage: variables = [var("w" + str(i),domain=ZZ)for i in range(s.nvertices())]
sage: eq
(w0 + w1 + w2 - 14*w3, w1 + 2*w2 - 8*w3, 2*w2 - 3*w3)
sage: result
[w0 == 15/2*r548, w1 == 5*r548, w2 == 3/2*r548, w3 == r548]
up to here it'
>
> > > [X] minus/plus
> >
> > > [X] '-'/'+'
> >
> > > [ ] below/above
> >
> > > [X] left/right
> >
> > > [ ] from_left/from_right
> >
> > My votes are the same as Rob's.
>
> Also my votes are the same as Rob's :)
>
Ditto.
Jason
--
To post to this group, send an email to sage-devel@googlegroup
On 29 čnc, 18:39, Jason Grout wrote:
> On 7/29/10 9:22 AM, Rob Beezer wrote:
>
> > I'm going to undiplomatically poison the well as I'll be offline for
> > the next few days. I like minus/plus and '-'/'+' as a package, like
> > left/right, and would not miss below/above. With good documentatio
>
> Burcin, earlier you said that there wouldn't be any tab completion for
> "from_left" and "from_right." Why is that? Does this have to do with
> my patch or how Sage handles tab completion? Is the default syntax
> for a given command the only one that shows up for tab completion?
>
I think
Please forgive my ignorance is this is a stupid question.
When creating worksheets in a Sage notebook, I often find myself
wishing that I could type text in the tinyMCE editor using wiki-syntax
(any would do fine) instead of using the current editor and
occasionally having to go to the HTML view a
> > [X] minus/plus
>
> > [X] '-'/'+'
>
> > [ ] below/above
>
> > [X] left/right
>
> > [ ] from_left/from_right
>
> My votes are the same as Rob's.
Ditto.
Burcin, earlier you said that there wouldn't be any tab completion for
"from_left" and "from_right." Why is that? Does this have to do with
m
Part 3, point #3 at
http://hub.opensolaris.org/bin/view/Community+Group+on/2008080405
says:
"you can put a [trusted] section into your own .hgrc"
Not a good solution universally, but maybe it will make a clone happen
for you?
On Jul 29, 8:11 am, Dima Pasechnik wrote:
> I tried on couple of ot
In characteristic 0 are there problems:
sage: T=SR(pAdicField(5)(1/3))
sage: T.pyobject()
2 + 3*5 + 5^2 + 3*5^3 + 5^4 + 3*5^5 + 5^6 + 3*5^7 + 5^8 + 3*5^9 + 5^10
+ 3*5^11 + 5^12 + 3*5^13 + 5^14 + 3*5^15 + 5^16 + 3*5^17 + 5^18 +
3*5^19 + O(5^20)
(fair enough - it just gets wrapped)
sage: T=SR(pAdi
On Jul 29, 9:51 am, Simon King wrote:
> 4)
> sage: SR(p)
> BOOM
shouldn't there at least be some consistency in the *characteristic*
of the symbolic ring? I can see how someone might want to make a
"symbolic ring of characteristic p", but mixing different
characteristics can't possibly lead to g
Hello, Carl.
Here is some documentation about Python-ALGLIB interface (called
X-interface in this document):
http://www.alglib.net/share/2010-07-26-alglib-for-sage/x-interface.pdf
It is very short, but should give a hint about meaning of all these
functions, expectations, functionality
Hi!
While trying to answer some post on sage-support I found the following
four problems.
Definitions:
sage: R. = GF(2^4)
sage: P. = R[]
sage: C = [t, t + 1, t^3 + t + 1, t^3 + 1, t^3 + t^2]
sage: p = P(C)
Do you agree that these are bugs?
1)
When doing P?, the documenation of P.__call__ is inc
On 7/29/10 9:22 AM, Rob Beezer wrote:
I'm going to undiplomatically poison the well as I'll be offline for
the next few days. I like minus/plus and '-'/'+' as a package, like
left/right, and would not miss below/above. With good documentation,
I'm less concerned about clutter.
[X] minus/plus
I'm going to undiplomatically poison the well as I'll be offline for
the next few days. I like minus/plus and '-'/'+' as a package, like
left/right, and would not miss below/above. With good documentation,
I'm less concerned about clutter.
[X] minus/plus
[X] '-'/'+'
[ ] below/above
[X] left/r
That is, without setting NUM_THREADS or something. I tried
./sage -testall -p 8
but I just get lots of error messages in addition to my test output.
I guess I have the same question about sage -tnew as well.
Thanks,
- kcrisman
--
To post to this group, send an email to sage-devel@googlegroups
A rough summary so far. Correct me if you think I have not read
comments correctly. Status quo is below/above and minus/plus and a
patch to add from_left/from_right.
* left/right is preferable to from_left/from_right
* a suggestion to deprecate below/above, with no objections,
and some
I suppose python takes care of this, or else the minus sign would cause some
issues.
For future reference to those who write LaTeX, you can use various hyphens
depending on whether or not you want line-breaking. (I.e., so
"line-breaking" can or cannot be split between lines at the hyphen.) I've
te
I tried on couple of other systems, and got pretty much the same
problem.
All is needed is to be logged in as an ordinary user, different from
the one owning the sage
installation. The following is on my laptop (sage install owned by
dima, and logged in as guest)
gu...@pasechnik1:~/test$ sage -clo
Hello,
I started rmpoly (http://code.google.com/p/rmpoly/),
a pure Python library for multivariate polynomials and power series on
QQ.
I tried the benchmarks on series truncated with the total degree in
http://www.mail-archive.com/sage-t...@googlegroups.com/msg42090.html
MPowerSeriesRing (MSR) wit
On Thursday, July 29, 2010, Dima Pasechnik wrote:
> I guess it boils down to whether "should" means "must" here, or not.
> Are there any means to decide, any precedents?
>
> (I can also contact authors and ask whether they might soften the
> language...)
Yes and you should definitely write to the
I guess it boils down to whether "should" means "must" here, or not.
Are there any means to decide, any precedents?
(I can also contact authors and ask whether they might soften the
language...)
Thanks,
Dima
On Jul 28, 9:43 pm, William Stein wrote:
> On Wed, Jul 28, 2010 at 11:30 AM, David Joy
On 07/29/10 02:12 PM, kcrisman wrote:
I will point out, though, that you clearly *do* use Maxima, since you
tried to do this in Sage, which uses Maxima heavily. One of the
things Sage has gotten a lot better about is acknowledging use of all
the many high-quality components, so let's all try t
Apparently there is a new Sage forum (and other open source math
software fora) out there, perhaps sponsored by whoever does Scilab:
http://www.equalis.com/forums/posts.asp?topic=119819&;
- kcrisman
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this
>
> For me, I use "is" when comparing with None, and if I specifically want
> *True* or *False* (e.g., if I don't want the empty list to count as False).
>
Yes, these were the sorts of situations I encountered.
- kcrisman
--
To post to this group, send an email to sage-devel@googlegroups.com
T
Great, these are now #9638 and #9639.
- kcrisman
On Jul 29, 2:32 am, Jason Grout wrote:
> On 7/28/10 11:31 AM, Harald Schilly wrote:
>
> > On Jul 28, 6:07 pm, kcrisman wrote:
> >> 1) Endpoint markers for the sliders.
>
> > I think that was already requested some time ago, I'm not sure, and I
>
On Jul 29, 3:38 am, Henryk Trappmann wrote:
> On Jul 28, 5:47 pm, Burcin Erocal wrote:
>
> > Can you open a ticket about these problems with the binomial (including
> > the "either m or x-m must be an integer" error mentioned in kcrisman's
> > message?
> > The bug in maxima for the evaluation o
Hi Simon and Florent,
Let me answer you both in one post, since I think your solutions might
be related. I agree with Simon that this is the offending line:
tester.assert_(isinstance(self,
self.parent().category().element_class))
Now, by adding the line
Element = DifferentialForm
to my p
There are two very minor issues with the spkg/standard/deps file. Both are
"cosmetic", in the sense they don't change the build order of any packages, but
both will add a bit of clarity to the file.
1) R depends on Fortran, though that is not very clear.
http://trac.sagemath.org/sage_trac/tick
> everything works well (no output), but when I run F._test_elements() I
> get an error in ... _test_category(). The precise error is listed
> below, but the traceback tells me that the problem arose in
> element.pyx:
>
> if not is_extension_type(self.__class__):
> # For usual Python
> +1 on the '+' and '-'. If we had that syntax, that's what I'd teach my
> > students to use since they'd already be using it in the classroom.
>
I'm +1 here too. I'm just paranoid and wondering if non-English/American
keyboard layouts will provide one of the 9+ unicode hyphen characters that
isn
On Jul 28, 5:47 pm, Burcin Erocal wrote:
> Can you open a ticket about these problems with the binomial (including
> the "either m or x-m must be an integer" error mentioned in kcrisman's
> message?
> The bug in maxima for the evaluation of the sum should also be a
> separate ticket.
I opened the
For the record, I have a proposed solution for this at #9614.
Dan
--
--- Dan Drake
- http://mathsci.kaist.ac.kr/~drake
---
signature.asc
Description: Digital signature
On Wed, Jul 28, 2010 at 10:56 PM, Rob Beezer wrote:
> It would appear that the �...@cached_function decorator prevents the
> decorated function from appearing in the HTML reference manual.
> Evidence is
>
> sage.functions.special.maxima_function()
> sage.structure.dynamic_class.dynamic_class_inte
On Wed, Jul 28, 2010 at 11:30 PM, Jason Grout
wrote:
> On 7/27/10 12:23 PM, D.C. Ernst wrote:
>
>> I'm not particularly in love with "from_*" and I am certainly
>> agreeable to changing it (as suggested earlier or otherwise). Can we
>> use the symbols "+" and "-"? This most closed mimics the sta
42 matches
Mail list logo
