Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #44914 > unrolled thread
| Started by | Chris Angelico <rosuav@gmail.com> |
|---|---|
| First post | 2013-05-08 09:04 +1000 |
| Last post | 2013-05-08 09:04 +1000 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Making safe file names Chris Angelico <rosuav@gmail.com> - 2013-05-08 09:04 +1000
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2013-05-08 09:04 +1000 |
| Subject | Re: Making safe file names |
| Message-ID | <mailman.1425.1367967872.3114.python-list@python.org> |
On Wed, May 8, 2013 at 8:18 AM, Fábio Santos <fabiosantosart@gmail.com> wrote: > I suggest Base64. b64encode > (http://docs.python.org/2/library/base64.html#base64.b64encode) and > b64decode take an argument which allows you to eliminate the pesky "/" > character. It's reversible and simple. But it doesn't look anything like the original. I'd be inclined to go for something like quoted-printable or URL-encoding; special characters become much longer, but ordinary characters (mostly) stay as themselves. ChrisA
Back to top | Article view | comp.lang.python
csiph-web