Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #29187
| From | Terry Reedy <tjreedy@udel.edu> |
|---|---|
| Subject | Re: Least-lossy string.encode to us-ascii? |
| Date | 2012-09-14 16:43 -0400 |
| References | <mailman.640.1347571498.27098.python-list@python.org> <725b3dd0-bd2b-404e-a261-ffe306b38c2f@googlegroups.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.719.1347655504.27098.python-list@python.org> (permalink) |
On 9/14/2012 12:15 PM, wxjmfauth@gmail.com wrote: > PS Avoid Py3.3 :-) pps Start using 3.3 as soon as possible. It has Python's first fully portable non-buggy Unicode implementation. The second release candidate is already out. -- Terry Jan Reedy
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Least-lossy string.encode to us-ascii? Tim Chase <python.list@tim.thechases.com> - 2012-09-13 16:26 -0500
Re: Least-lossy string.encode to us-ascii? Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-09-14 03:49 +0000
Re: Least-lossy string.encode to us-ascii? wxjmfauth@gmail.com - 2012-09-14 09:15 -0700
Re: Least-lossy string.encode to us-ascii? Terry Reedy <tjreedy@udel.edu> - 2012-09-14 16:43 -0400
Re: Least-lossy string.encode to us-ascii? wxjmfauth@gmail.com - 2012-09-15 01:58 -0700
Re: Least-lossy string.encode to us-ascii? wxjmfauth@gmail.com - 2012-09-15 01:58 -0700
Re: Least-lossy string.encode to us-ascii? wxjmfauth@gmail.com - 2012-09-14 09:15 -0700
csiph-web