[issue35084] binascii.Error: Incorrect padding

Change by Irit Katriel : -- resolution: -> third party stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[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

Terry J. Reedy added the comment: TestUser, please re-read and follow Serhiy's request. -- nosy: +terry.reedy ___ Python tracker ___

[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 > > ___ > Python tracker >

[issue35084] binascii.Error: Incorrect padding

Karthikeyan Singaravelan added the comment: @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

[issue35084] binascii.Error: Incorrect padding

Change by Serhiy Storchaka : -- Removed message: https://bugs.python.org/msg329061 ___ Python tracker ___ ___ Python-bugs-list

[issue35084] binascii.Error: Incorrect padding

Serhiy Storchaka added the comment: Don't include quoted full messages of other users. Only include quoted fragments if it is absolutely necessary. -- nosy: +serhiy.storchaka ___ Python tracker

[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 is the crash reports use of

[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

Karthikeyan Singaravelan added the comment: Can you please add your definition of a crash? Crash in bug report context is used in C language context like causing a segfault, buffer overflow etc. Proper Exceptions are not considered as a crash and this is an exception raised since the

[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 on this bug

[issue35084] binascii.Error: Incorrect padding

Braden Groom added the comment: The file contents that you've provided aren't valid base64. I think the traceback that you've received is a reasonable one. -- nosy: +bradengroom ___ Python tracker

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

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

[issue35084] binascii.Error: Incorrect padding

Karthikeyan Singaravelan added the comment: Thanks for the report. Can you please attach the file test.code1? Your original report says "test.code1" is not base64 encoded and -d takes a file that is base64 encoded and decodes it. Can you please be more descriptive about what you are

[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__", mod_spec) File