[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [cantor] [Bug 375467] Cantor hangs at "Initializing Session" when choosing Sage backend (Sage versio
From:       Alexander Semke <bugzilla_noreply () kde ! org>
Date:       2018-05-15 15:52:48
Message-ID: bug-375467-17878-qx0BxLNBLv () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=375467

--- Comment #16 from Alexander Semke <alexander.semke@web.de> ---
(In reply to Nikita Sirgienko from comment #13)
> (In reply to Antonio Rojas from comment #12)
> > It does, indeed. (Sage 8.2, ipython 5.6.0)
> Well, thanks for report.
> Now, this changes in sage file fix this bug, but you lose color in sage
> output.
> So, I create feature request ticket for Sage:
> https://trac.sagemath.org/ticket/25363
> If the ticket will be accepted (for example, in sage 8.3), I add version
> dependent fix, which will be fix sage backend for sage >= 8.3 (but sage <
> 8.3 still be broken) without color losing in sage output.
> 
> I also maybe report prompt_toolkit about problem with multiline input for
> (pseudo)terminal devices. However, it also fix the sage backend only for
> future versions
> 
> Theoretically, If there is way to run 'sage-ipython' directly, without sage
> bash file, I guess, that I could fix this bug for all sage versions, but I
> am not sure.
Wouldn't it be better if the main sage bash script would simply forward the CLI
parameters to sage-ipython. With this we'd simply always call sage with
--simple-promt or the user will provide this parameter explicitly in cantor
settings for sage where the user already has to specify the path for sage. With
this solution it would be up to the sage's user/frontend to specify this
parameter or not and there is no need to always use it as proposed in your trac
ticket.

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]