Skip to content

Conversation

@sanjayankur31
Copy link
Member

  • uses logging where appropriate,
  • removes print_comment_v, and makes print_comment the default pretty printed comment function. It'll always print. For debuginfo and warnings and so on, we use the loggers.

@sanjayankur31 sanjayankur31 added the T: enhancement Type: enhancement label Jul 5, 2021
@sanjayankur31 sanjayankur31 self-assigned this Jul 5, 2021
@sanjayankur31 sanjayankur31 linked an issue Jul 5, 2021 that may be closed by this pull request
@sanjayankur31
Copy link
Member Author

Refactoring, mostly with cosmetic changes. All tests pass, so confirmation that this hasn't broken any functionality. Merging (so I can open more PRs, which will otherwise conflict with this one).

@sanjayankur31 sanjayankur31 merged commit 0b645d6 into development Jul 6, 2021
@sanjayankur31 sanjayankur31 deleted the feat/use-logging branch July 6, 2021 09:41
@pgleeson
Copy link
Member

pgleeson commented Jul 6, 2021

Thanks @sanjayankur31 . From a qucik test I see that the output from jnml, which had been displayed by default when run in pynml does not show any more. This is useful debugging info. Can you change that?

@sanjayankur31
Copy link
Member Author

Sure---since it is debugging info, it can be seen when -v INFO or -v DEBUG are provided. Do we always want this info to be always shown to users?

@sanjayankur31
Copy link
Member Author

If a command fails, it will be printed: these are at the CRITICAL level. For example: https://github.com/NeuroML/pyNeuroML/blob/development/pyneuroml/pynml.py#L1649

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

T: enhancement Type: enhancement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Replace print_comment* methods with a logging class implementation

3 participants