-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[REF] Use logging instead of printed statements #65
Conversation
I'm not sure why this is failing tests - it seems to be internal to CircleCI, not due to any code changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. But why did the PR go away?
I got really bogged down working on PICAchooser this weekend - came back to finish accepting this, and the PR seems to have been closed without being accepted. Did you pull it? |
Uh oh - something seems a bit wonky. Logging is throwing a lot of errors on the test run (but completing). Command follows:
Results below:
|
Ah, yeah, that's one I missed when I switched from printing to logging. LGR.info("validvoxels shape =", numvalidspatiallocs) with LGR.info(f"validvoxels shape = {numvalidspatiallocs}") |
Ah ok. That will help inspire me to fully embrace f strings :-). |
Closes #41.
To do:
memprofile
with memory usage logger. I'm still not sure what it's for, but I'll figure it out.Changes proposed in this pull request:
verbose
anddebug
if statements. The logger natively handles different levels of messages, although I did have to add a new level for the verbose messages.fftpack
import. Will need to be propagated across the package.