Re: Neither pdb or print() displays the bug [FIXED]

On Tue, 1 Jun 2021, Rich Shepard wrote: I'm stuck with neither approach (pdb, print()) working. I moved the database code to a separate module, datasource.py, and when I run the activitytypes.py module (using pdb and having entered print() statements at various places in both the datasource and

Re: Neither pdb or print() displays the bug

On Sun, 6 Jun 2021, Fabio Zadrozny wrote: Hint: you should be able to use https://pypi.org/project/pytest-qt/ to unit-test a PyQt application... Fabio, Thank you for confirming this. I hadn't remembered the name so your URL is really helpful. Regards, Rich -- https://mail.python.org/mailman

Re: Neither pdb or print() displays the bug

Em qua., 2 de jun. de 2021 às 09:34, Rich Shepard escreveu: > On Wed, 2 Jun 2021, Peter Otten wrote: > > > Do you have unit tests? Those are an excellent tool to ensure that the > > components of an application work as expected and that those components > > have well-defined interfaces. Debugging

Re: Neither pdb or print() displays the bug

On Wed, 2 Jun 2021, Peter Otten wrote: Do you have unit tests? Those are an excellent tool to ensure that the components of an application work as expected and that those components have well-defined interfaces. Debugging a failing unittest is usually easier than to debug a complex application.

Re: Neither pdb or print() displays the bug

On 01/06/2021 23:32, Rich Shepard wrote: On Tue, 1 Jun 2021, Ethan Furman wrote: Well, you only had two logging statements in that code -- logging is like print: if you want to see it, you have to call it: Ethan, Got it, thanks. I believe Do you have unit tests? Those are an excellent too

Re: Neither pdb or print() displays the bug

On 01/06/2021 21:18, Rich Shepard wrote: > On Sun, 30 May 2021, Cameron Simpson wrote: > >> I've only just started with pdb. As of Python 3.7 there's a builtin >> function named breakpoint() which drops you into the debugger. > I'm stuck with neither approach (pdb, print()) working. > The act

Re: Neither pdb or print() displays the bug

On Tue, 1 Jun 2021, Dennis Lee Bieber wrote: I suspect you really should be stepping INTO the calls, not just invoking the functions completely and going to the next LOCAL statement. $ /development/business_tracker/activitytypes.py(1)() -> import sys (Pdb) s $ /development/business_

Re: Neither pdb or print() displays the bug

On Tue, 1 Jun 2021, Ethan Furman wrote: Well, you only had two logging statements in that code -- logging is like print: if you want to see it, you have to call it: Ethan, Got it, thanks. I believe my problem is with the datasource module. I'm focused on making it work (using logging to conf

Re: Neither pdb or print() displays the bug

On 6/1/21 1:42 PM, Rich Shepard wrote: > When I run it this is the output: > $ python activitytypes.py 2021-06-01 13:39:10,219 -DEBUG - Start of Program > 2021-06-01 13:39:15,229 -DEBUG - End of Program Well, you only had two logging statements in that code -- logging is like print: if you want

Re: Neither pdb or print() displays the bug

On Tue, 1 Jun 2021, Ethan Furman wrote: Sounds like a console issue. Try using `logging` with a file... you could even use `print` with a file if you wanted to. Ethan, Not before using logging I found a reference/example page

Re: Neither pdb or print() displays the bug

On Tue, 1 Jun 2021, Rich Shepard wrote: The QSize() statement is never reached. Correction: the window is 800 x 600, but it's still empty. Rich -- https://mail.python.org/mailman/listinfo/python-list

Re: Neither pdb or print() displays the bug

On 6/1/21 1:18 PM, Rich Shepard wrote: > I'd appreciate recommendations on the process to find where the bug lives > since I can't seem to find it with print() or line-by-line in pdb. Sounds like a console issue. Try using `logging` with a file... you could even use `print` with a file if you

Neither pdb or print() displays the bug

On Sun, 30 May 2021, Cameron Simpson wrote: I've only just started with pdb. As of Python 3.7 there's a builtin function named breakpoint() which drops you into the debugger. I've never been a big debugger person, historicly using print() and equivalent. However, this makes it very easy to inser