> > Should I post this on trac? Should an inferior sage always make sure
> > %pdb is turned off, or should the pexpect interface handle ipdb prompts?
>
> I am not sure if this is something we want or should work around. My
> POV on this is as mentioned above if you do custom ipython/ipythonrc
> s
On Apr 21, 4:52 pm, "Nicolas M. Thiery"
wrote:
Hi Nicolas,
> Oops, running late reading sage-devel ...
:)
> Well, you might be disappointed: in my case it turns out that this
> probably stems from the fact that I have %pdb on by default (pdb 1 in
> ipython/ipythonrc).
Ok, having non-defaul
Oops, running late reading sage-devel ...
On Thu, Apr 16, 2009 at 02:34:24PM -0700, mabshoff wrote:
> On Apr 16, 9:30 am, "Nicolas M. Thiery"
> wrote:
> > On Wed, Apr 15, 2009 at 11:56:37PM -0700, mabshoff wrote:
>
>
>
> > > > Anyone getting the same behaviour?
> >
> > > I have seen it fail o
On Apr 16, 9:30 am, "Nicolas M. Thiery"
wrote:
> On Wed, Apr 15, 2009 at 11:56:37PM -0700, mabshoff wrote:
> > > Anyone getting the same behaviour?
>
> > I have seen it fail on occasion, but not reproducibly. Does that fail
> > for you every time in the same spot?
>
> Over a dozen run, it se
On Apr 16, 2009, at 9:30 AM, Nicolas M. Thiery wrote:
>
> On Wed, Apr 15, 2009 at 11:56:37PM -0700, mabshoff wrote:
>>
>>
>>
>> On Apr 15, 11:54 pm, "Nicolas M. Thiery"
>> wrote:
>>> Hello!
>>>
>>> With my sage 3.4, which unless I screwed up is a plain sage 3.4,
>>>
>>> sage -t -
On Wed, Apr 15, 2009 at 11:56:37PM -0700, mabshoff wrote:
>
>
>
> On Apr 15, 11:54 pm, "Nicolas M. Thiery"
> wrote:
> > Hello!
> >
> > With my sage 3.4, which unless I screwed up is a plain sage 3.4,
> >
> > sage -t -verbose sage/interfaces/sage0.py
> >
> > hangs forever at:
>
On Apr 15, 11:54 pm, "Nicolas M. Thiery"
wrote:
> Hello!
>
> With my sage 3.4, which unless I screwed up is a plain sage 3.4,
>
> sage -t -verbose sage/interfaces/sage0.py
>
> hangs forever at:
>
> Trying:
> sage0.get('x')###line 354:_sage_ >>> sage0.get(
