Missing guards after argparse for bad arg combinations
madeddy opened this issue · 1 comments
madeddy commented
(Tracking issue to have it noted and don't gets forgotten.)
At the moment, as of unrpyc v2.0 / v1.3, its possible to use certain argparse arg combinations which will not work and fail mostly silently. This includes TL issues like mentioned in #202, but some can be there resolved with the described refactoring.
Known bad combis:
- no_pyexpr and comparable args without dump (mentioned but not blocked from usage)
- translation args with dump or deobfuscation
-
combinations of translation args with each other
If someone knows more bad combinations just drop them here. So far... Guards for this already done, in testing and will be at some point added.
madeddy commented
combinations of translation args with each other
This will not possible anymore if the translate PR gets merged so i close this issue as concluded.