Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #97464 > unrolled thread
| Started by | Ben Finney <ben+python@benfinney.id.au> |
|---|---|
| First post | 2015-10-07 10:24 +1100 |
| Last post | 2015-10-07 10:24 +1100 |
| 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: Python 2 ‘print’, coercing arguments to Unicode Ben Finney <ben+python@benfinney.id.au> - 2015-10-07 10:24 +1100
| From | Ben Finney <ben+python@benfinney.id.au> |
|---|---|
| Date | 2015-10-07 10:24 +1100 |
| Subject | Re: Python 2 ‘print’, coercing arguments to Unicode |
| Message-ID | <mailman.440.1444173909.28679.python-list@python.org> |
Terry Reedy <tjreedy@udel.edu> writes: > On 10/6/2015 6:45 AM, Ben Finney wrote: > > Ben Finney <ben+python@benfinney.id.au> writes: > > > How can I convince ‘print’, everywhere throughout a module, that it > > should coerce its arguments using ‘unicode’? > > Use Python 3. I am only half joking. Switching to unicode instead > of bytes as the default text type fixed numerous bugs all at once. This is all part of a transition to Python 3, so I am fully on board with that. It doesn't help address the problem to tell me I want to do what I'm already in pursuit of doing :-) -- \ “Intellectual property is to the 21st century what the slave | `\ trade was to the 16th.” —David Mertz | _o__) | Ben Finney
Back to top | Article view | comp.lang.python
csiph-web