@Tester Thanks for the report. I looked at the crash report and I couldn't see CPython crashing with a segfault. I think it's a crash from another application which might be running the interpreter and can't handle the error raised by CPython for invalid data being decoded. This is something the application which crashes has to handle when CPython returns the expected trace back and I don't see any fix from CPython's end. Correct me if I am wrong here.

Relevant CPython trace back : 

PythonArgs: ['/usr/lib/python3.6/base64.py', '-d', 'test.code2']
Traceback:
 Traceback (most recent call last):
   File "/usr/lib/python3.6/runpy.py", line 193, in _run_module_as_main
     "__main__", mod_spec)
   File "/usr/lib/python3.6/runpy.py", line 85, in _run_code
     exec(code, run_globals)
   File "/usr/lib/python3.6/base64.py", line 602, in <module>
     main()
   File "/usr/lib/python3.6/base64.py", line 586, in main
     func(f, sys.stdout.buffer)
   File "/usr/lib/python3.6/base64.py", line 512, in decode
     s = binascii.a2b_base64(line)
 binascii.Error: Incorrect padding


Please remove the quoted content while replying from email since it's added to the bug tracker and causes scrolling a little difficult with duplicated content.


Thanks