On Monday, October 16, 2017 at 11:58:12 PM UTC-7, Steve D'Aprano wrote:
> On Tue, 17 Oct 2017 03:06 pm, llanitedave wrote:
>
> [...]
> > I set up the logging code at the very beginning of the app, before any other
> > work is done. Here's the relevant code:
> >
> > #!/usr/bin/env python3
> [...
Those are some good suggestions, I've found that I won't be able to work on it
today, but I'll definitely follow up tomorrow. As for not showing all the
code, the main window and its associated code are definitely there and working.
I didn't post it because of all the setup code for fields and
On Tue, 17 Oct 2017 03:06 pm, llanitedave wrote:
[...]
> I set up the logging code at the very beginning of the app, before any other
> work is done. Here's the relevant code:
>
> #!/usr/bin/env python3
[... snip imports ...]
> class MainWindow(QMainWindow):
> def __init__(self):
> s
On Tue, Oct 17, 2017 at 3:06 PM, llanitedave
wrote:
> I'm building an application that contains some long-running operations in a
> separate thread from the user interface. I've been using the logging module
> writing logging.info() statements to a .log file to keep track of the data
> interac
I'm building an application that contains some long-running operations in a
separate thread from the user interface. I've been using the logging module
writing logging.info() statements to a .log file to keep track of the data
interactions while it runs.
In the midst of a recent run, the loggi
