Add method to get user defined command line arguments in unittest.main

[remilapeyre]

BPO	36036
Nosy	@remilapeyre
Files	0001-WIP.patch

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2019-02-19.13:06:20.832>
labels = ['3.8', 'library']
title = 'Add method to get user defined command line arguments in unittest.main'
updated_at = <Date 2019-02-19.13:06:29.857>
user = 'https://github.com/remilapeyre'

bugs.python.org fields:

activity = <Date 2019-02-19.13:06:29.857>
actor = 'remi.lapeyre'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-02-19.13:06:20.832>
creator = 'remi.lapeyre'
dependencies = []
files = ['48154']
hgrepos = []
issue_num = 36036
keywords = ['patch']
message_count = 1.0
messages = ['335944']
nosy_count = 1.0
nosy_names = ['remi.lapeyre']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue36036'
versions = ['Python 3.8']

[remilapeyre]

Hi, I'm working on bpo-18765 (running pdb.post_mortem() on failing test cases) where I need to control the behavior of a TestCase based on some outside input.

For this issue, I want to add a new --pdb option to turn this feature on when enabled. As of today, it seems to me that the command line arguments given to the TestProgram are not accessible from the TestCase.

Would adding a new parameter to TestCase be breaking backward compatibility? If so, what would be a better way to access command line arguments from TestCase?

In addition to this, I have the need for another project to change the behavior of TestCases based on a custom command line argument. I propose to add a new method getCustomArguments that will take the parser as input so the user can define it's own arguments by subclassing TestProgram

What do you think about this?