logger names bug

[keara-soloway]

In this pipeline:

- common.NexusReader:
    filename: data.nxs
    nxpath: structured_data
- common.PrintProcessor

The logger for the common.NexusReader somehow ends up named common.PrintProcessor which leads to confusing log statements like

...
2026-04-06 08:29:39: Pipeline            : INFO: Calling "execute" on NexusReader
2026-04-06 08:29:39: common.PrintProcessor: DEBUG: Executing "read" with schema "None" and {}
2026-04-06 08:29:39: common.PrintProcessor: INFO: Executing "read"
2026-04-06 08:29:39: common.PrintProcessor: INFO: Finished "<bound method NexusReader.read of NexusReader(root=PosixPath('<BLAH>'), inputdir=PosixPath('/<BLAH>'), outputdir=PosixPath('<BLAH>'), interactive=False, log_level='DEBUG', logger=<Logger common.PrintProcessor (DEBUG)>, name='NexusReader', schema_=None, filename='<BLAH>/data.nxs', nxpath='structured_data', idx=None, mode='r', nxmemory=None)>" in 0 seconds
...

[keara-soloway]

I think the general case is: any item immediate preceding a PrintProcessor has the (usually incorrect) logger name common.PrintProcessor.

[rolfverberg]

Resolved:
commit be5e0b0
Author: Rolf Verberg rv43@cornell.edu
Date: Tue Jul 7 16:17:35 2026 -0400

refactor: a bunch of if else to minimize pylint nesting issues

commit b5814e8
Author: Rolf Verberg rv43@cornell.edu
Date: Tue Jul 7 16:08:51 2026 -0400

fix: logger fixed when the pipeline item is a string (issue 268)

Also refactors a bunch of if ... else ... to minimize nesting issues
in pylint