On Tue, Feb 8, 2011 at 5:20 PM, William Stein wrote:
> If you're interested in coming to Seattle during our spring break
> (when campus is pretty empty and the weather is nice), it looks highly
> likely I'll be able to run a big Sage Days workshop. Please send me
> an email (wst...@gmail.com) if
On 2/22/11 5:17 PM, Justin C. Walker wrote:
On Feb 22, 2011, at 14:52 , Jason Grout wrote:
On 2/22/11 3:10 PM, Justin C. Walker wrote:
On Feb 22, 2011, at 11:44 , Jason Grout wrote:
I don't see what you see; perhaps one of us has sufficiently strange setup in
our startup files to either m
On Feb 22, 2011, at 14:52 , Jason Grout wrote:
> On 2/22/11 3:10 PM, Justin C. Walker wrote:
>>
>> On Feb 22, 2011, at 11:44 , Jason Grout wrote:
>>
>>
>> I don't see what you see; perhaps one of us has sufficiently strange setup
>> in our startup files to either mask or cause the problems.
>
On Feb 22, 2011, at 13:15 , Jason Grout wrote:
> On 2/22/11 3:10 PM, Justin C. Walker wrote:
>>
>> On Feb 22, 2011, at 11:44 , Jason Grout wrote:
[snip]
> Can you try the other simpler test?
>
> bash-3.2$ PATH='.';export PATH
> bash-3.2$ /usr/libexec/path_helper -s
> PATH="/usr/bin:/bin:/usr/sbi
On 02/22/11 10:52 PM, Jason Grout wrote:
On 2/22/11 3:10 PM, Justin C. Walker wrote:
On Feb 22, 2011, at 11:44 , Jason Grout wrote:
I don't see what you see; perhaps one of us has sufficiently strange
setup in our startup files to either mask or cause the problems.
It might be that I my def
On 02/22/11 03:49 PM, rjf wrote:
A parser for the maxima language is not only easier to write,
it is available in source form. It is also based on a well known
technique which is also used by Reduce. The real difficulty is
to implement a Mathematica language parser, since the language
fails to fi
On 2/22/11 3:10 PM, Justin C. Walker wrote:
On Feb 22, 2011, at 11:44 , Jason Grout wrote:
I don't see what you see; perhaps one of us has sufficiently strange setup in
our startup files to either mask or cause the problems.
It might be that I my default shell set to zsh. Could you try cha
On 2/22/11 2:19 PM, Jason Grout wrote:
There are lots of times when it would be convenient to have the
documentation of various spkgs installed in a local or system Sage
installation. For example, it seems that I'm always wishing that I had
that at an airport or on an airplane. At one point a lon
On 2/22/11 3:10 PM, Justin C. Walker wrote:
On Feb 22, 2011, at 11:44 , Jason Grout wrote:
On OSX, the path_helper command is always executed when starting a new shell.
Unfortunately, the path_helper command prepends standard system values to the
PATH variable, which means that the Sage-spe
On Feb 22, 2011, at 11:44 , Jason Grout wrote:
> On OSX, the path_helper command is always executed when starting a new shell.
> Unfortunately, the path_helper command prepends standard system values to
> the PATH variable, which means that the Sage-specific values come at the end
> of the PA
On Feb 22, 3:19 pm, Jason Grout wrote:
> There are lots of times when it would be convenient to have the
> documentation of various spkgs installed in a local or system Sage
> installation. For example, it seems that I'm always wishing that I had
> that at an airport or on an airplane. At one
There are lots of times when it would be convenient to have the
documentation of various spkgs installed in a local or system Sage
installation. For example, it seems that I'm always wishing that I had
that at an airport or on an airplane. At one point a long time ago, we
had an extradocs spk
On OSX, the path_helper command is always executed when starting a new
shell. Unfortunately, the path_helper command prepends standard system
values to the PATH variable, which means that the Sage-specific values
come at the end of the PATH variable. This causes all sorts of breakage
when try
On Tue, Feb 22, 2011 at 12:40 AM, Keshav Kini wrote:
> On Feb 22, 3:08 pm, Robert Bradshaw
> wrote:
>> On Mon, Feb 21, 2011 at 8:26 PM, Eviatar wrote:
>> > Importing in a loop is definitely not a good idea.
>>
>> Unless the loop is rarely executed...
>>
>> > I found this great guide about Python
On Tue, Feb 22, 2011 at 7:00 AM, kcrisman wrote:
>
>
> On Feb 22, 3:48 am, Keshav Kini wrote:
>> On Feb 22, 3:25 pm, Keshav Kini wrote:
>>
>> > For example the construction
>>
>> > "stuff %s stuff" % dictionary
>>
>> > is deprecated and in fact does not even work in Python 3.
>>
>> Oops - sorry,
> While I assume that some people at WRI may be observing the Sage
Yes, I can definitely confirm this.
> activity, I doubt that they feel Sage breathing down their necks.
I agree - so far. But it was amazing how many visitors we had at the
JMM booth talking about doing an institutional switch. I
A parser for the maxima language is not only easier to write,
it is available in source form. It is also based on a well known
technique which is also used by Reduce. The real difficulty is
to implement a Mathematica language parser, since the language
fails to fit the standard expectations for com
On Feb 22, 3:48 am, Keshav Kini wrote:
> On Feb 22, 3:25 pm, Keshav Kini wrote:
>
> > For example the construction
>
> > "stuff %s stuff" % dictionary
>
> > is deprecated and in fact does not even work in Python 3.
>
> Oops - sorry, this is wrong. It still works in Python 3.1, but
> according t
I built the Jmol .spkg simply so people could test it. What I suggest
is that this .spkg be folded into the next sagenb release. I suppose
if I am to help after that I will have to figure out how you are
maintaining the shared code. I work regularly with SVN and CVS, but
have no experience with
On Feb 22, 3:25 pm, Keshav Kini wrote:
> For example the construction
>
> "stuff %s stuff" % dictionary
>
> is deprecated and in fact does not even work in Python 3.
Oops - sorry, this is wrong. It still works in Python 3.1, but
according to http://docs.python.org/release/3.1.2/whatsnew/3.0.html
Hi Kwankyu,
This is exactly what I have just written into the documentation (see
trac #10782 ) and posted about on this list a couple of days ago
(
http://groups.google.com/group/sage-devel/browse_thread/thread/b18d052bf057d465
).
Hope that helps!
-Keshav
On Feb 22, 3:13 pm, Kwankyu Lee wrote
On Feb 22, 3:08 pm, Robert Bradshaw
wrote:
> On Mon, Feb 21, 2011 at 8:26 PM, Eviatar wrote:
> > Importing in a loop is definitely not a good idea.
>
> Unless the loop is rarely executed...
>
> > I found this great guide about Python performance, including
> > information about importing, lazy im
22 matches
Mail list logo
