Windows base64 Decode

[ahirreddy]

BPO	3595
Nosy	@vstinner, @ericvsmith, @ezio-melotti

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2009-02-27.00:11:57.367>
created_at = <Date 2008-08-19.02:24:44.593>
labels = ['invalid', 'library']
title = 'Windows base64 Decode'
updated_at = <Date 2009-02-27.00:11:57.366>
user = 'https://bugs.python.org/ahirreddy'

bugs.python.org fields:

activity = <Date 2009-02-27.00:11:57.366>
actor = 'vstinner'
assignee = 'none'
closed = True
closed_date = <Date 2009-02-27.00:11:57.367>
closer = 'vstinner'
components = ['Library (Lib)']
creation = <Date 2008-08-19.02:24:44.593>
creator = 'ahirreddy'
dependencies = []
files = []
hgrepos = []
issue_num = 3595
keywords = []
message_count = 4.0
messages = ['71400', '71759', '82518', '82796']
nosy_count = 4.0
nosy_names = ['vstinner', 'eric.smith', 'ezio.melotti', 'ahirreddy']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue3595'
versions = ['Python 2.5']

[ahirreddy]

I'm new to this and not quite sure how to go about posting an issue, but
I will do the best I can. In Python 2.5.2, both from python.org and
active state, all methods of decoding in base64 under Windows produce
different output than base64 decoding under UNIX (I've tested it both on
OS X and Linux, which produce the same results). I ran into this while
writing a script that downloads email and parses mime attachments which
are base64 encoded by a similar upload script. UNIX systems are able to
download the attachments and decode the base64 back to the original
attachments correctly, which I've verified with md5sum hashes. The same
script under windows produces an incorrect file. At first I was not sure
what the issue was, and I eventually wrote the raw base64 attachment to
a file. I then used a windows command line tool to decode the file and
it produced the correct output (again checked by md5sum). This leads me
to believe that something is strange with base64 under Windows. I hope
my explanation has helped some. If need be I'll upload the script so
others can replicate my results.

Ahir

[ericvsmith]

Please upload your script, or (preferably) some small test code.

I suspect the problem is related to line endings and binary versus text
files.

[ezio-melotti]

This can be closed if Ahir doesn't provide the script.

[vstinner]

need more informations like a test script. reopen if you such
script ;-)