Mathieu Villion

I plus that. If you use a single interface for multiple scripts, it can be handy to simply ignore --unwanted-option otherwise you need either: - run a pre-parsing stage to...

Imagine I have a script that censors bad words and raises an error when bad words are present in file : `python censor_bad_words.py [--language=]` and another script which simply prints...

"Would you apply it only on option -s short option, --long-option or would it also apply to or command too?" All arguments that do not match the definition are rejected....

Rinex 4.0 files can be found in BRD400DLR https://igs.org/mgex/mgex-product-descriptions/#1642582637650-aebf3e85-1704

Might be related to: https://github.com/geospace-code/georinex/issues/65

Same issue, "command line options" are ignored when using the Debugger. If I use Run file (F5) with "run this file in:" Debugger, debugger starts with command line options but...

[ These commands were working in Spyder 5: In [5]: runfile("/home/user/test.py", args="--feat=027b") --> ok In [6]: debugfile("/home/user/test.py", args="--feat=027b") UsageError: unrecognized arguments: args=--feat=027b) ] The suggested workaround is working: %debugfile /home/user/test.py...