have been addressed anyway with the patch
> in trac ticket #4127 (that went into Sage 3.1.3.alpha0), but Michael
> Abshoff and David Philp should please have another look at the issue.
>
> If I can be of any help (testing, more discussion), just let me know,
> I've got both a PPC
>
> Would it be excessively uncivilised to *automatically* change the
> path during the build process?
Well, the kind of people who will come across it will be capable of
changing their own path---and maybe sensitive. And, it might require
root permissions.
D
> >
--~--~-~--~-
Glad it eventually worked for you. Sorry I forgot to mention the
readline bug. My brain is not big enough to remember all those steps.
It does cause a doctest failure.
As you probably have realized, Michael already has a patch for it in
the pipeline, it will be fixed in 3.1.2 I believe. If
On 06/09/2008, at 3:27 AM, mabshoff wrote:
> The Framework build of Sage
Do we have a framework build of sage? We have an unsupported
framework build of python, and R can be built as a framework, but
turning sage itself into a framework would be a kind of huge job. I
doubt it would be v
Hi
On 06/09/2008, at 3:21 AM, Simon Beaumont wrote:
>
> I tried building sage 3.0.1 with David Philps patches - make failed
> first with the r build looking for sage (which is in there somewhere
R sometimes fails to build if fink is findable. I don't think that is
related to any frameworks.
From the discussion in sage-support (which I mistook for sage-devel).
On 02/09/2008, at 6:22, Robert Dodier <[EMAIL PROTECTED]> wrote:
> * sets and matrices not distinguished from lists
Mathematica's attributes are something I will miss in Sage. (They are
a partial fix for some of the probl
On 29/08/2008, at 9:29 AM, Simon Beaumont wrote:
> On Aug 28, 11:22 pm, David Philp <[EMAIL PROTECTED]> wrote:
>> On 29/08/2008, at 7:56 AM, mabshoff wrote:
>>
>>> David Philip has been playing with building PyCuDA against Sage's
>>> Python on OSX.
On 29/08/2008, at 7:56 AM, mabshoff wrote:
> David Philip has been playing with building PyCuDA against Sage's
> Python on OSX.
No!!! I'd love to do it but I haven't got time for CUDA. I've been
using boost.python, for the sake of /other/ C++ code of mine. I
originally tried to sort of bo
On 26/08/2008, at 5:09 PM, Burcin Erocal wrote:
> In[]:= Assuming[0 Out[]= ArcCos[Cos[x]]
In[]:= Simplify[ArcCos[Cos[x]], Assumptions -> 0 < x < Pi/2]
Out[] = x
==
David J Philp
Postdoctoral Fellow
National Centre for Epidemiology and Population Health
Building 6
On 26/08/2008, at 2:12 PM, William Stein wrote:
>> I actually don't understand this. For both pynac and the existing
>> maxima link, I think you must already have some method of
>> transforming
>> a python object to and from lisp-like expressions.
>
> Pynac works with objects that are simply
On 26/08/2008, at 12:42 PM, William Stein wrote:
> 1) Let me clarify -- I *wrapped* the pattern matching already in
> Pynac.
...
> and you
> can read about Ginac at the Ginac website: http://www.ginac.de/
Thanks for the clarification. Sorry I missed the post about pynac---
I'm fairly quick
On 26/08/2008, at 8:15 AM, Ondrej Certik wrote:
>> Is "not extending of Maxima" a concrete policy? I understand that
>> maxima
>> sucks in some circumstances, but it seems quite the beast here.
>> I am quite confused about a lot of the pattern matching
>> discussion. AFAICT,
>> that is the
On 26/08/2008, at 2:50 AM, William Stein wrote:
> Burcin -- I did actually mostly implement pattern matching in Pynac.
Is there documentation? A bit of google turned up nothing.
>sage: sin(1+sin(x)).subs(sin(w0)==cos(w0))
>cos(cos(x) + 1)
In Mathematica, the result wou
On 24/08/2008, at 6:15 AM, William Stein wrote:
>
> On Sat, Aug 23, 2008 at 1:00 PM, Fredrik Johansson
> <[EMAIL PROTECTED]> wrote:
>>
>> On Sat, Aug 23, 2008 at 9:57 PM, Nils Bruin <[EMAIL PROTECTED]> wrote:
>>>
>>> Would it break Python too much if comparison would simply throw an
>>> exceptio
On 23/08/2008, at 3:43 AM, Harald Schilly wrote:
> For me, python is a different playground than mma and unless there
> isn't a real reason i don't like to import mma syntax - or any other.
I would much prefer to learn the proper python way of doing things
than try to retrofit python to make
On 23/08/2008, at 1:04 AM, Robert Dodier wrote:
> The Mma operators /. #& -> etc are just doing things that might
> just as well be represented as ordinary functions.
> Wouldn't it be much clearer, and much less hackish, to just make
> them functions and stay entirely within Python?
Not function
A few days ago I spent a couple of hours getting PyObjC working with
sage. The objective was to be able to write little sage-based GUI
applications. (Though it could easily turn into a full-blown sage.app
IDE, that was outside the scope of 2 hours playing around.)
The basic notion of PyO
On 22/08/2008, at 5:27 PM, William Stein wrote:
>
> On Thu, Aug 21, 2008 at 11:28 PM, David Philp
> <[EMAIL PROTECTED]> wrote:
>
>> I hope one can't own such things but I don't want a legal fight.
>
> If I were afraid, then Sage would be nowher
On 22/08/2008, at 3:34 PM, William Stein wrote:
>
> On Thu, Aug 21, 2008 at 9:41 PM, Arnaud Bergeron
> <[EMAIL PROTECTED]> wrote:
>>
> data /. x_?(# < 0 &) -> 0 (this is perhaps not the killer example)
What does that do?
>>>
>>> /. is the pattern replacement operator, _ is a plac
>> [EMAIL PROTECTED] (elegant, clear, no matching of brackets)
>
> What does that do?
Sorry! I didn't want to go into detail unless people didn't already
know it.
Same as f[data]. Benefit is that you can chain it up really clearly.
[EMAIL PROTECTED]@[EMAIL PROTECTED] is better than f[g[h[x
On 22/08/2008, at 11:10 AM, Ondrej Certik wrote:
> what are the chances that maxima could be made fast, so that people
> intuitively feel it's as fast as mathematica for the problems they
> solve
It may already have been said, but a large part of the reason it feels
slow is that AFAICT maxima
On 22/08/2008, at 11:00 AM, Mike Hansen wrote:
>> The documentation system I want to see is a centralised wiki. It
>> works like this:
>> help(var) gets you the [locally cached] copy of the documentation.
>
> I think these are two orthogonal problems. Do you mean something like
> this http://s
On 22/08/2008, at 10:35 AM, Mike Hansen wrote:
>
> Hello all,
>
> Carl Witty and I wrote a proposal for the use of the Sphinx
> documentation system in Sage. It can be found at
> http://wiki.sagemath.org/SphinxSEP We'd appreciate any comments /
> questions / concerns that people have.
The docu
On 22/08/2008, at 5:18 AM, William Stein wrote:
> Please ask questions, make comments, and keep this thread going!
I don't know how much of the below is possible or available in Sage.
But I miss they syntax from Mathematica. I love the fact that it
doesn't wear down the little fingers on
On 20/08/2008, at 1:41 AM, Nick Alexander wrote:
>
>> Hence, deleting unneeded portions helps the reader.
>
> Strong +1. This list is particularly bad for quoting an entire
> message, 5 levels deep, only to add "I agree" at the very end.
I don't feel strongly about it. But I am much more lik
On 15/08/2008, at 12:49 PM, David Philp wrote:
>
> Hi
>
>>> I forgot to mention that this is boost 1.35.0. I assume it is a
>>> difference between the boosts, because sage is unlikely to have
>>> changed without you noticing. I am now compiling sage 3.0.3 a
Hi...
This doesn't seem to be the hottest topic of all time.
More below.
On 12/07/2008, at 12:16 AM, mabshoff wrote:
> On Jul 10, 11:23 pm, David Philp <[EMAIL PROTECTED]> wrote:
>
> Hi David,
>
>> R does not work inside sage if LD_LIBRARY_PATH includes /sw
On 14/07/2008, at 8:06 AM, Dr. David Kirkby wrote:
> On Jul 13, 10:42 pm, Harald Schilly <[EMAIL PROTECTED]> wrote:
>
>> You forget one point (for me the probably biggest one) - the
>> community. Especially around matlab you have a wide range of "open
>> source" (public domain, do what you want.
R does not work inside sage if LD_LIBRARY_PATH includes /sw/lib.
(Which it ordinarily wouldn't, that was a mistake of mine.) That bug
is pretty trivial and easily fixed.
But I found that R is the only component of sage that links to system
frameworks. (Aside from python.) That seems to
On 10/07/2008, at 2:04 PM, mabshoff wrote:
>> It should be fine. We used UCS2 until maybe 8 months ago. We
>> switched
>> as mentioned above only for Linux compatibility.
>>
>>> You will need to do this for each successive
>>> version of sage, which could be tedious.
>>
>> I would be ok with
>> Integrate[x^a, {x, 1, Infinity}] returns an answer that incorporates
>> assumptions:
>> If[Re[a] < -1, -(1/(1 + a)), Integrate[x^a, {x, 1, ∞}, Assumptions
>> ->
>> Re[a] >= -1]]
>>
>> If you want me to unpack that or have a more instructive example,
>> just
>> ask.
>>
> Forgot about that
On 10/07/2008, at 2:14 PM, François Bissey wrote:
>
> On Thu, 10 Jul 2008, Robert Dodier wrote:
>> William Stein wrote:
>>> If you answer could you summarize what Maple/Mathematica do
>>> (if you care), and if so why you think whatever you propose is
>>> better than them.
>>
>> Not sure if I am
This is a 'for the record' email describing how to use boost.python
with sage on Mac OS X. Thanks to the gentlefolk who walked me through
it (especially Carl Witty).
I am assuming a working boost.python extension called 'my_ext.so'.
"Working" means that you should be able to start up pyth
33 matches
Mail list logo
