On Jun 9, 2009, at 8:16 PM, Tim Lahey wrote:
> On Jun 9, 2009, at 11:09 PM, Nick Alexander wrote:
>
>>
Can you clarify with an example what you mean? In other words, can
you
give an example of the "new" way and the "old" way?
>>
>> And the examples with multiple variables?
>>
>> N
On Jun 8, 2009, at 12:26 PM, Pat LeSmithe wrote:
> John H Palmieri wrote:
>> On Jun 8, 8:42 am, Pat LeSmithe wrote:
>>> davidloeffler wrote:
Can I make a special request for this release? It would be
really nice
if we could get rid of the insufferable "WARNING: html_favicon
>>
On Jun 9, 2009, at 9:47 AM, Jason Bandlow wrote:
>> On Jun 9, 2009, at 8:29 AM, Jason Bandlow wrote:
>>
>>> Hi,
>>>
>>> I ran across the following behavior in sage-3.4.1 and sage-4.0 (I
>>> don't
>>> have 4.0.1 yet), and I find it fairly disturbing.
>>>
>>> sage: d = {'a': 1} # Create
On Jun 9, 2009, at 11:09 PM, Nick Alexander wrote:
>
>>> Can you clarify with an example what you mean? In other words, can
>>> you
>>> give an example of the "new" way and the "old" way?
>
> And the examples with multiple variables?
>
> Nick
The problem I have with the "new" way is that it is
>> Can you clarify with an example what you mean? In other words, can
>> you
>> give an example of the "new" way and the "old" way?
And the examples with multiple variables?
Nick
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroup
Hi,
On Tue, Jun 9, 2009 at 9:45 PM, Jason Grout wrote:
>> (4) Should we switch to old maxima format for "diff"?
>
> Can you clarify with an example what you mean? In other words, can you
> give an example of the "new" way and the "old" way?
In new symbolics, "df(x)/dx" is
(a) represented as:
Golam Mortuza Hossain wrote:
>
> (4) Should we switch to old maxima format for "diff"?
Can you clarify with an example what you mean? In other words, can you
give an example of the "new" way and the "old" way?
Thanks,
Jason
--~--~-~--~~~---~--~~
To post to
On Jun 9, 2009, at 8:01 PM, Golam Mortuza Hossain wrote:
>
> (4) Should we switch to old maxima format for "diff"?
>
Yes. At least make it the default and the other an option.
Cheers,
Tim.
---
Tim Lahey
PhD Candidate, Systems Design Engineering
University of Waterloo
http://www.linkedin.com/
Hello,
On Tue, Jun 9, 2009 at 3:00 PM, Dr. David Kirkby wrote:
> In Sage, this is not so, as typing 'make' after any edits to files will
> extract the original .spkg file, and overwrite ones edits. I know one
> could create a new .spkg file, but that is a long-winded way.
Which files are you edi
> (2) keyword "latex_name": If I understand correctly, the new
> "SFunction" class can be given keyboard argument
> "latex_name=LaTeX". Somehow, it doesn't seem to work
> from notebook. It would be really cool if we could define a
> symbolic function as
>
> riemann(x) = function('riemann',
Hi,
On Fri, Jun 5, 2009 at 7:09 PM, Mike Hansen wrote:
> The _latex_ from Expressions calls GiNaC which as code for assembling
> latex code from the expression tree. The thing that corresponds to
> SymbolicFunctionEvaluation is roughly sage.symbolic.function.SFunction
> and PrimitiveFunction.
Hello,
On Tue, Jun 9, 2009 at 4:51 PM, kcrisman wrote:
>
>
>>
>> This means that you can either not have (semi)private functions in
>> your code or any code submissions to sage will be automatically
>> rejected due to the 100% doctest requirement, unless I am overlooking
>> something silly.
>>
T
>
> This means that you can either not have (semi)private functions in
> your code or any code submissions to sage will be automatically
> rejected due to the 100% doctest requirement, unless I am overlooking
> something silly.
>
What I will say is probably silly, but sometimes it's tripped me u
I've created a tool chain for Solaris on t2, which I'm hoping solves the
gfortran issues. Certainly gcc-4.4.0 will compile fortran programs now
and it seems to get a long way to building Sage, although I do have an
error I hope to fix.
If anyone wishes to use it, please sent the following vari
Hi,
I have been looking for examples and searching the web site, but could
not find anything concerning the following problem:
If you copy the following code snippet into a file say doctest.py
def nounderscore(nn):
"""
EXAMPLES:
sage: nound
In most open-source program, which come as a set of source files, one
can change a file, type 'make' and the changes will be seen immediately.
In Sage, this is not so, as typing 'make' after any edits to files will
extract the original .spkg file, and overwrite ones edits. I know one
could cre
> I feel like the process of "download patches from a ticket, apply in
> some order, rebuild and test, and commit" makes sense as a menu-based
> text interface, especially if you want to do several in a row. Or am I
> the only one that likes that idea? I did spend too much time on MUDs
> in high s
Marshall Hampton wrote:
> That sounds awesome - convert the entire Sage development process to
> an online RPG, where the basic quests are merging tickets!
Fantastic. What can I do with my gold? And can we start a graph theory
clan (or whatever the groups are called)?
William's clan will pro
> On Jun 9, 2009, at 8:29 AM, Jason Bandlow wrote:
>
>> Hi,
>>
>> I ran across the following behavior in sage-3.4.1 and sage-4.0 (I
>> don't
>> have 4.0.1 yet), and I find it fairly disturbing.
>>
>> sage: d = {'a': 1} # Create some object
>> sage: d
>> {'a': 1}
>> sage: ty
That sounds awesome - convert the entire Sage development process to
an online RPG, where the basic quests are merging tickets!
-Marshall
On Jun 9, 3:34 am, Craig Citro wrote:
> > I've been
> > thinking about writing something like this up for a while now, but
> > there's never enough time to d
This isn't a coercion issue, it's because of how functions are
defined in Sage using the "f(x) = expr" notation using the preparser.
I think that's too useful to get rid of. We could special case a
warning for "type(x) = ..." but I'm not sure if that's the best idea.
- Robert
On Jun 9, 200
Hi,
I ran across the following behavior in sage-3.4.1 and sage-4.0 (I don't
have 4.0.1 yet), and I find it fairly disturbing.
sage: d = {'a': 1} # Create some object
sage: d
{'a': 1}
sage: type(d) = type({}) # Attempt to check the type but
2009/6/9 Carlo Hamalainen :
>
> Hi,
>
> Is anyone going to EuroPython 2009?http://www.europython.eu/
>
> I'm thinking of going and maybe doing a short talk on Sage but I
> haven't decided yet.
I see that it is happening in Birmingham which is 15 minutes up the
road from where I am (=Warwick).
2009/6/9 Carlo Hamalainen :
>
> Hi,
>
> Is anyone going to EuroPython 2009? http://www.europython.eu/
>
> I'm thinking of going and maybe doing a short talk on Sage but I
> haven't decided yet.
I hope you give a talk on Sage. I'm not going to EuroPython, since I
didn't know about it
and I'm g
Hi,
Is anyone going to EuroPython 2009?http://www.europython.eu/
I'm thinking of going and maybe doing a short talk on Sage but I
haven't decided yet.
--
Carlo Hamalainen
http://carlo-hamalainen.net
--~--~-~--~~~---~--~~
To post to this group, send email to
> I've been
> thinking about writing something like this up for a while now, but
> there's never enough time to do everything one wants to in Sage :)
>
For the record, I'm in the process of writing a first system for doing
this right now. It's mostly done (I can automatically get a string of
patc
2009/6/9 Robert Bradshaw :
>
> On Jun 9, 2009, at 1:17 AM, John Cremona wrote:
>
>>
Dream feature: having a button on the trac ticket web page that
would
run this script on sage.math (don't know if this is easily doable
though).
>>>
>>> I would envision that I would setup
On Jun 9, 2009, at 1:17 AM, John Cremona wrote:
>
>>>
>>> Dream feature: having a button on the trac ticket web page that
>>> would
>>> run this script on sage.math (don't know if this is easily doable
>>> though).
>>
>> I would envision that I would setup an always-running script on
>> sage.
2009/6/9 William Stein :
>
> 2009/6/8 Nicolas M. Thiery :
>>
>> On Tue, Jun 02, 2009 at 10:32:34AM -0700, William Stein wrote:
>>>
>>> On Tue, Jun 2, 2009 at 8:35 AM, kcrisman wrote:
>>> >
>>> >> > Come on, guys; is it really so hard to run "sage -docbuild reference
>>> >> > html" and check the o
29 matches
Mail list logo
