Skip to content
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

Wrong default name of html log #711

Open
k-dovgan opened this issue Mar 24, 2022 · 2 comments
Open

Wrong default name of html log #711

k-dovgan opened this issue Mar 24, 2022 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@k-dovgan
Copy link
Contributor

Currently when using the -hl option without any further specification the name of a created file is default (instead of expected universum_log.html).
Need to be expected, fixed and, maybe, covered by regression test

@k-dovgan k-dovgan added the bug Something isn't working label Mar 24, 2022
@dogbert911
Copy link
Collaborator

This issue is related to #703

@miltolstoy
Copy link
Collaborator

The current problem can be solved by #713, but a more general fix is needed to solve all similar situations (like #703).

Root issue - subparser arguments override main parser arguments with the same name:

./test.py --arg value1 subparser --arg value2
Namespace(arg='value2')

The current solution of the root issue - #715, appending the "default" parser.
But the current solution leads to issues like this one, so it should be done in some other way.

A preliminary investigation shows the possible way to resolve it.
Parser settings:

parser.add_argument("--arg", dest="main_arg")
subparser.add_argument("--arg", dest="subparser_arg")

Usage:

./test.py --arg value1 subparser --arg value2
Namespace(main_arg='value1', subparser_arg='value2')

Possible CLI help formatting issues can be resolved based on this StackOverflow information - https://stackoverflow.com/a/56595689

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants