Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #44909
| References | <51895D03.4000300@gmail.com> |
|---|---|
| Date | 2013-05-07 23:18 +0100 |
| Subject | Re: Making safe file names |
| From | Fábio Santos <fabiosantosart@gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.1422.1367965130.3114.python-list@python.org> (permalink) |
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. More suggestions: how about a hash? Or just use IDs from the database? On Tue, May 7, 2013 at 8:58 PM, Andrew Berg <bahamutzero8825@gmail.com> wrote: > Currently, I keep Last.fm artist data caches to avoid unnecessary API calls and have been naming the files using the artist name. However, > artist names can have characters that are not allowed in file names for most file systems (e.g., C/A/T has forward slashes). Are there any > recommended strategies for naming such files while avoiding conflicts (I wouldn't want to run into problems for an artist named C-A-T or > CAT, for example)? I'd like to make the files easily identifiable, and there really are no limits on what characters can be in an artist name. > -- > CPython 3.3.1 | Windows NT 6.2.9200 / FreeBSD 9.1 > -- > http://mail.python.org/mailman/listinfo/python-list -- Fábio Santos
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Making safe file names Fábio Santos <fabiosantosart@gmail.com> - 2013-05-07 23:18 +0100
csiph-web