[issue35084] binascii.Error: Incorrect padding

TestUser added the comment: One of the problems reporting is the archaic way the bug trackers work. Sorry fo the confusion except I am not sure of the exact request. On my end I have provided what I can. You are welcome to fire up a VM and run the sample submitted. All the best. On Fri, Nov

[issue35084] binascii.Error: Incorrect padding

TestUser added the comment: Last thought ... man base64 has different options than the program: python3 -m base64 -d -i test.code2 option -i not recognized usage: /usr/lib/python3.6/base64.py [-d|-e|-u|-t] [file|-] -d, -u: decode -e: encode (default) -t: encode and

[issue35084] binascii.Error: Incorrect padding

TestUser added the comment: My guess is the Gnome terminal. It does not like non ASCI data. There are other programs that generate segfaults in the terminal when piped random binary data. Maybe, Python could get a -Q quit setting to turn of the trace back? Thanks On Thu, Nov 1, 2018 at 9:18

[issue35084] binascii.Error: Incorrect padding

TestUser added the comment: That is all the crash automator provides. On Thu, Nov 1, 2018 at 9:13 AM Serhiy Storchaka wrote: > > Change by Serhiy Storchaka : > > > -- > Removed message: https://bugs.python.org/msg329061 > >

[issue35084] binascii.Error: Incorrect padding

TestUser added the comment: On Mon, Oct 29, 2018 at 4:03 PM TestUser wrote: > > TestUser added the comment: > > In the new version of Ubuntu this generates a system crash report. Normally > I delete them. > > Give me a day or to to get you one. > > Funny, since it

[issue35084] binascii.Error: Incorrect padding

TestUser added the comment: In the new version of Ubuntu this generates a system crash report. Normally I delete them. Give me a day or to to get you one. Funny, since it is the crash reports use of base64 encoding that led me to the Python base64 module. On Sun, Oct 28, 2018 at 8:42 PM

[issue35084] binascii.Error: Incorrect padding

TestUser added the comment: Thanks. The Python Foundation asked for users to report bugs. I've done so. I'm looking at putting this in an article and Tweets on the bug process: generating bugs, reporting, and resolution. If I go forward I would like a thought or two from you o

[issue35084] binascii.Error: Incorrect padding

TestUser added the comment: FYI: This error generates an Ubuntu Crash Report. Every time I use it on the CLI. I wonder how many of these are generated? On Sun, Oct 28, 2018 at 3:49 PM TestUser wrote: > > TestUser added the comment: > > The file contained the fo

[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: > >

[issue35084] binascii.Error: Incorrect padding

TestUser added the comment: The file contained the following code: 0x11a3ff119c\xe3\x50\x89\xe2\x53\x89\xe1\xb0\x0b\xcd\x80#%^ciuqrfiqrYWJjMTIzIT8kKiYoKSctPUB- abc123! On Sun, Oct 28, 2018 at 1:35 AM Karthikeyan Singaravelan < rep...@bugs.python.org> wrote: > > Karthikeyan

[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_a

[issue35084] binascii.Error: Incorrect padding

New submission from TestUser : The below "test.code1" is not base64 encoded. Though, it is a good file. t:~$ python3 -m base64 -d test.code1 Traceback (most recent call last): File "/usr/lib/python3.6/runpy.py", line 193, in _run_module_as_main "__main__&quo