I didn't do much with setting traces / breakpoints from within the Python
code itself in the tutorial. You can call from pudb import set_trace as bp;
bp() to launch the pudb debugger at a certain point in the code. This
should simplify having to manually add all of the breakpoints from within
the P
And if you do "sage -sh" first, then it'll use a different pudb
installed into sage.
(sorry for spamming the list)
On Fri, Dec 9, 2016 at 10:19 AM, William Stein wrote:
> Also, pudb is now pre-installed systemwide so `pip install pudb` is no
> longer needed
>
> On Fri, Dec 9, 2016 at 10:16 A
Also, pudb is now pre-installed systemwide so `pip install pudb` is no
longer needed
On Fri, Dec 9, 2016 at 10:16 AM, William Stein wrote:
> On Fri, Dec 9, 2016 at 9:58 AM, William Stein wrote:
>> On Fri, Dec 9, 2016 at 8:07 AM, Maxie Schmidt wrote:
>>> For the sake of completeness, I'm add
On Fri, Dec 9, 2016 at 8:07 AM, Maxie Schmidt wrote:
> For the sake of completeness, I'm adding a link to a SMC wiki tutorial on
> using PUDB with Sage (for both local source installs and within the SMC
> terminal application):
> https://github.com/sagemathinc/smc/wiki/Using-a-GUI-Python-Debugger-
Also, if the group can help me figure out how to get extra add-on python
modules installed with Sage, I'd be happy to write up a tutorial on how to
get the stock python memory profiler and PUDB working with Sage.
Maxie
On Nov 28, 2016 3:37 PM, "Maxie Schmidt" wrote:
> I'm looking for an ncurses
I'm looking for an ncurses-like GUI debugging tool. PUDB looks especially
nice from what I can find online. Is there anything else like this for
Sage? My searches came up empty.
There's sort of a secondary question buried in the first question I asked,
which is how to get add-on modules, like the
