Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #109919
| From | Dennis Lee Bieber <wlfraed@ix.netcom.com> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: base64.b64encode(data) |
| Date | 2016-06-13 20:20 -0400 |
| Organization | IISS Elusive Unicorn |
| Message-ID | <mailman.49.1465863653.2288.python-list@python.org> (permalink) |
| References | (4 earlier) <1465795993.2881334.635716385.023A423E@webmail.messagingengine.com> <mailman.28.1465795996.2288.python-list@python.org> <575e8c77$0$1599$c3e8da3$5496439d@news.astraweb.com> <1465824966.3931239.636067473.06E0521B@webmail.messagingengine.com> <p8julbdjgmbghumec6g7uhul2d6e5g9t2g@4ax.com> |
On Mon, 13 Jun 2016 09:36:06 -0400, Random832 <random832@fastmail.com>
declaimed the following:
>
>Sure. But let's not pretend that U+0020 through U+007E *aren't* unicode
>characters. Base 64's output is characters. Those characters could be
>encoded as ASCII, as UTF-32, as EBCDIC, and they would still be the same
>characters.
>
But, as mentioned, ASCII and (to a lesser extant) EBCDIC are 1-byte per
character encodings, and are safe on 8-bit transports (ASCII on 7-bit!)
since no single byte of BASE64 would appear as any sort of control
character... The transport could include a stage punching a paper tape
which is manually moved to another system for reading.
--
Wulfraed Dennis Lee Bieber AF6VN
wlfraed@ix.netcom.com HTTP://wlfraed.home.netcom.com/
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
base64.b64encode(data) Marcin Rak <mrak@sightlineinnovation.com> - 2016-06-12 11:56 -0700
Re: base64.b64encode(data) Marko Rauhamaa <marko@pacujo.net> - 2016-06-12 22:26 +0300
Re: base64.b64encode(data) Steven D'Aprano <steve@pearwood.info> - 2016-06-13 12:22 +1000
Re: base64.b64encode(data) Random832 <random832@fastmail.com> - 2016-06-12 23:20 -0400
Re: base64.b64encode(data) Steven D'Aprano <steve@pearwood.info> - 2016-06-13 15:16 +1000
Re: base64.b64encode(data) Random832 <random832@fastmail.com> - 2016-06-13 01:33 -0400
Re: base64.b64encode(data) Marko Rauhamaa <marko@pacujo.net> - 2016-06-13 09:45 +0300
Re: base64.b64encode(data) Steven D'Aprano <steve@pearwood.info> - 2016-06-13 20:35 +1000
Re: base64.b64encode(data) Random832 <random832@fastmail.com> - 2016-06-13 09:36 -0400
Re: base64.b64encode(data) Steven D'Aprano <steve@pearwood.info> - 2016-06-22 01:56 +1000
Re: base64.b64encode(data) Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2016-06-13 20:20 -0400
Re: base64.b64encode(data) Michael Torrie <torriem@gmail.com> - 2016-06-13 09:15 -0600
Re: base64.b64encode(data) Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2016-06-14 11:04 +1200
Re: base64.b64encode(data) Chris Angelico <rosuav@gmail.com> - 2016-06-14 03:07 +1000
Re: base64.b64encode(data) Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2016-06-14 11:12 +1200
Re: base64.b64encode(data) Random832 <random832@fastmail.com> - 2016-06-13 21:19 -0400
csiph-web