[issue35085] FileNotFoundError: [Errno 2] No such file or directory:

Change by Steven D'Aprano : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue35085] FileNotFoundError: [Errno 2] No such file or directory:

TestUser added the comment: How can that be CLI useful. Lucky I guess as this does not generate a Crash Report. OK. Bad/Missing File would have been my preferred. Then again? Thanks On Sun, Oct 28, 2018 at 1:48 AM Karthikeyan Singaravelan < rep...@bugs.python.org> wrote: > > Karthikeyan

[issue35085] FileNotFoundError: [Errno 2] No such file or directory:

Karthikeyan Singaravelan added the comment: I can see one another related report issue35084. As @steven.daprano said this is an expected traceback and it's working correctly. -d expects a valid base64 encoded file and supplying a non-existent file or file with invalid encoding is supposed

[issue35085] FileNotFoundError: [Errno 2] No such file or directory:

Steven D'Aprano added the comment: What do you mean, a crash report? You get a traceback telling you the problem: the file is missing. What behaviour did you expect if you try to decode a non-existent file? Perhaps you meant to write: python3 -m base64 -t "12s345a2" I don't think this is

[issue35085] FileNotFoundError: [Errno 2] No such file or directory:

New submission from TestUser : Seems the base64 module has issues with bad file(s). This does not seems to generate a Crash Report. t:~$ python3 -m base64 -d "12s345a2" Traceback (most recent call last): File "/usr/lib/python3.6/runpy.py", line 193, in _run_module_as_main "__main__",