This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ahirreddy
Recipients ahirreddy
Date 2008-08-19.02:24:42
SpamBayes Score 2.3524743e-07
Marked as misclassified No
Message-id <1219112685.57.0.506715853146.issue3595@psf.upfronthosting.co.za>
In-reply-to
Content
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
History
Date User Action Args
2008-08-19 02:24:45ahirreddysetrecipients: + ahirreddy
2008-08-19 02:24:45ahirreddysetmessageid: <1219112685.57.0.506715853146.issue3595@psf.upfronthosting.co.za>
2008-08-19 02:24:44ahirreddylinkissue3595 messages
2008-08-19 02:24:43ahirreddycreate