> On Nov 5, 2011, at 18:02 , Burcin Erocal wrote:
> > On Sat, 5 Nov 2011 17:23:38 -0700 (PDT)
> >
> > leif wrote:
> >> On 5 Nov., 21:24, "Justin C. Walker" wrote:
> >>> On Nov 5, 2011, at 12:16 , Julien Puydt wrote:
> Le 05/11/2011 17:42, William Stein a écrit :
> > What do you base thi
leif wrote:
Thomas Oliveira wrote:
Now, sage runs without throwing any warning.
Let me summarizing how I followed your advices to a next user that faces
this problem:
$ touch spkg/installed/readline-6.2.p2
$ sudo apt-get install libncurses5-dev libncursesw5-dev
Verified that $SAGE_ROOT/spkg/
On Nov 5, 2011, at 18:02 , Burcin Erocal wrote:
> On Sat, 5 Nov 2011 17:23:38 -0700 (PDT)
> leif wrote:
>
>> On 5 Nov., 21:24, "Justin C. Walker" wrote:
>>> On Nov 5, 2011, at 12:16 , Julien Puydt wrote:
>>>
Le 05/11/2011 17:42, William Stein a écrit :
> What do you base this "probab
On Sat, 5 Nov 2011 17:23:38 -0700 (PDT)
leif wrote:
> On 5 Nov., 21:24, "Justin C. Walker" wrote:
> > On Nov 5, 2011, at 12:16 , Julien Puydt wrote:
> >
> > > Le 05/11/2011 17:42, William Stein a écrit :
> > >> What do you base this "probably" on? Having started and watched
> > >> Sage "evolve"
Thomas Oliveira wrote:
> Now, sage runs without throwing any warning.
>
> Let me summarizing how I followed your advices to a next user that faces
> this problem:
>
> $ touch spkg/installed/readline-6.2.p2
>
> $ sudo apt-get install libncurses5-dev libncursesw5-dev
>
> Verified that $SAGE_ROOT/
On Saturday 05 November 2011, John H Palmieri wrote:
> Well, as I mentioned above, the current plan in #11790 is, among other
> things, to source a file ~/.sage/.sagerc (if it exists), so maybe you can
> add code to set your prompt there.
That sounds like a great plan.
Cheers,
Martin
--
name: Ma
On Nov 5, 4:32 am, leif wrote:
> john.hoebing wrote:
> > The solution is to replace ./spkg/standard/readline-6.1* with
> > readline-6.2.p2.spkg and then go to the sage home directory and run
> > 'make distclean' and then run 'make'. The 'libreadline*' files that
> > are already built (and used
On 5 Nov., 21:24, "Justin C. Walker" wrote:
> On Nov 5, 2011, at 12:16 , Julien Puydt wrote:
>
> > Le 05/11/2011 17:42, William Stein a écrit :
> >> What do you base this "probably" on? Having started and watched Sage
> >> "evolve" of over 6 years, if anything it is not evolving in the
> >> direc
Thomas Oliveira wrote:
> $ ./sage --python -c "import readline"
>
> gives
>
> Traceback (most recent call last):
> File "", line 1, in
> ImportError: No module named readline
Ok, your Python spkg apparently wasn't (re)built after you installed the
readline-6.2.p2 spkg. To do so, run
$ ./sag
Well, as I mentioned above, the current plan in #11790 is, among other
things, to source a file ~/.sage/.sagerc (if it exists), so maybe you can
add code to set your prompt there.
--
John
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, se
On Nov 5, 2011, at 3:44 PM, Martin Albrecht wrote:
>>> case "$SHELL_NAME" in
>
> It's not that terribly important, by this wouldn't work for my ZShell prompt
> because i use more advanced features in my prompt. In particular, my prompt
> displays the revision number of the hg repository I'm in
On Nov 4, 9:03 pm, kcrisman wrote:
> Well, we're currently just assessing interest; I'm sure it would be
> possible to do it closer in, but then we'd need someplace different to
> do it. I have no idea whether the usual suspects in Cambridge or some
> of the other Boston institutions (or CMI wher
On Nov 5, 2011, at 12:16 , Julien Puydt wrote:
> Le 05/11/2011 17:42, William Stein a écrit :
>> What do you base this "probably" on? Having started and watched Sage
>> "evolve" of over 6 years, if anything it is not evolving in the
>> direction you suggest.
>
> Fair point. But that can't last.
On Sat, Nov 5, 2011 at 12:16 PM, Julien Puydt wrote:
> Le 05/11/2011 17:42, William Stein a écrit :
>>
>> What do you base this "probably" on? Having started and watched Sage
>> "evolve" of over 6 years, if anything it is not evolving in the
>> direction you suggest.
>
> Fair point. But that can'
Le 05/11/2011 17:42, William Stein a écrit :
What do you base this "probably" on? Having started and watched Sage
"evolve" of over 6 years, if anything it is not evolving in the
direction you suggest.
Fair point. But that can't last.
All the libs and programs on my system weight 9G, with many
On 2011-11-05 15:44, Martin Albrecht wrote:
>>> case "$SHELL_NAME" in
>
> It's not that terribly important, by this wouldn't work for my ZShell prompt
> because i use more advanced features in my prompt. In particular, my prompt
> displays the revision number of the hg repository I'm in and whet
On 5 Nov., 15:44, Martin Albrecht
wrote:
> > > case "$SHELL_NAME" in
>
> It's not that terribly important, by this wouldn't work for my ZShell prompt
> because i use more advanced features in my prompt. In particular, my prompt
> displays the revision number of the hg repository I'm in and whether
Well the best thing would be if you didn't import paralel
in multi_polynomial_ideal.py. You should first write some decorators like
leif mentioned based on the trick that Tom showed so it will become easy to
make functions have multiple implementations. So that something like the
following woul
On 11/5/11 12:00 PM, William Stein wrote:
On Sat, Nov 5, 2011 at 9:40 AM, Jason Grout wrote:
On 11/5/11 11:37 AM, William Stein wrote:
It certainly seems possible.
I'm restarting the *.sagenb.org servers, since it would be nice for
people to be able to use them...
I already restarted sage
On Sat, Nov 5, 2011 at 9:40 AM, Jason Grout wrote:
> On 11/5/11 11:37 AM, William Stein wrote:
>
>> It certainly seems possible.
>>
>> I'm restarting the *.sagenb.org servers, since it would be nice for
>> people to be able to use them...
>>
>
> I already restarted sagenb.org. I think I've restar
So, the solution is to move the parallel importation to somewhere
else? Which would be the apropriate place?
On 5 nov, 14:28, Maarten Derickx wrote:
> The problem is that by putting
>
> from sage.parallel.all import parallel
>
> in sage/rings/polynomial/multi_polynomial_ideal.py you changed the i
On Sat, Nov 5, 2011 at 7:26 AM, Julien Puydt wrote:
> Le 05/11/2011 14:31, Jeroen Demeyer a écrit :
>>
>> On 2011-11-04 08:19, Julien Puydt wrote:
>>>
>>> but rather a more deliberately fragile one :
>>> - check very-specific-arch1, and set magic options if so ;
>>> ...
>>> - check very-specific-a
On 11/5/11 11:37 AM, William Stein wrote:
It certainly seems possible.
I'm restarting the *.sagenb.org servers, since it would be nice for
people to be able to use them...
I already restarted sagenb.org. I think I've restarted sagenb.org maybe
2-3 times in the past 2 weeks for this problem
On Sat, Nov 5, 2011 at 7:51 AM, Jason Grout wrote:
> Yet again, sagenb.org is throwing lots of errors like:
>
> 2011-11-05 07:30:38-0700 [-] Unhandled Error
> Traceback (most recent call last):
> File
> "/sagenb/sage_install/sage-4.7/local/lib/python2.6/site-packages/Twisted-9.0.0-
Yet again, sagenb.org is throwing lots of errors like:
2011-11-05 07:30:38-0700 [-] Unhandled Error
Traceback (most recent call last):
File
"/sagenb/sage_install/sage-4.7/local/lib/python2.6/site-packages/Twisted-9.0.0-py2.6-linux-x86_64.egg/twisted/application/app.py",
line 4
> > case "$SHELL_NAME" in
It's not that terribly important, by this wouldn't work for my ZShell prompt
because i use more advanced features in my prompt. In particular, my prompt
displays the revision number of the hg repository I'm in and whether it's
clean or not. Hence, additional modules ne
Le 05/11/2011 14:31, Jeroen Demeyer a écrit :
On 2011-11-04 08:19, Julien Puydt wrote:
but rather a more deliberately fragile one :
- check very-specific-arch1, and set magic options if so ;
...
- check very-specific-archN, and set magic options if so ;
- if we aren't on a known arch, or a fly f
On 2011-11-04 08:19, Julien Puydt wrote:
> but rather a more deliberately fragile one :
> - check very-specific-arch1, and set magic options if so ;
> ...
> - check very-specific-archN, and set magic options if so ;
> - if we aren't on a known arch, or a fly farted too near a known one :
> FAIL.
Th
The problem is that by putting
from sage.parallel.all import parallel
in sage/rings/polynomial/multi_polynomial_ideal.py you changed the import
order of the sage library causing the import to fail because now you try to
import QuotientRing from the not yet completely initialized quotient_ring
>From a clean sage braaanch, i put the line
from sage.parallel.all import parallel
in sage/rings/polynomial/multi_polynomial_ideal.py and after
rebuilding i get the following output when starting up sage:
--
| Sage Version 4.7.2
On Wednesday, November 2, 2011 9:11:12 AM UTC+8, leif wrote:
>
> On 2 Nov., 01:22, Keshav Kini wrote:
> > Another possibility is to set PS1 in the new shell to an expanded PS1
> from
> > the old shell by creating a dynamic string:
> >
> > fs@zhenghe ~/tmp $ echo "export PS1=\"(sage -sh) $PS
31 matches
Mail list logo
