jayvdb added a comment.
The blocking '<x> argument conflict' tasks are all the overlaps/conflicts that I could detect.
The -user conflicts are an example where the library arg parsing should consume that argument and not give it to scripts, and ideally somehow detect it is being used. This could be done by handle_args returning a special string class which emits a deprecation warning whenever it is compared with a global argument.
The others are conflicts with pagegen arguments, and do not necessarily block the arg parse task, as some support for argument conflicts must be supported anyway, but solving some of them may mean we can deprecate support of some argument names being re-implemented in scripts.
TASK DETAIL https://phabricator.wikimedia.org/T76429
EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: XZise, jayvdb Cc: jayvdb, Ricordisamoa, Ladsgroup, XZise, pywikipedia-bugs