Message347999
I took a stab at this, see attached PR.
I was able encode the first two cases described by @tarek, but not the first one because `_parse_command_opts` doesn't have visibility to the list of global options that have already been parsed.
Note:
I had to move `log.set_verbosity(self.verbose)` after the call to `_parse_command_opts` in order to correctly apply the verbosity level after all command options are parsed. I think there should be a better way to handle this case, maybe by creating a `verbose` setter that re-runs `log.set_verbosity` every time `verbose` value is updated. |
|
Date |
User |
Action |
Args |
2019-07-16 02:35:40 | potomak | set | recipients:
+ potomak, zooko, tarek, eric.araujo, dstufft, zvyn, avi |
2019-07-16 02:35:40 | potomak | set | messageid: <1563244540.5.0.0656069216099.issue7202@roundup.psfhosted.org> |
2019-07-16 02:35:40 | potomak | link | issue7202 messages |
2019-07-16 02:35:39 | potomak | create | |
|