Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #63246
| References | <lablra$1mc$2@ger.gmane.org> <lacmi3$kfq$1@ger.gmane.org> <lacq0d$k2e$1@ger.gmane.org> <52C9EEAF.4000702@stoneleaf.us> |
|---|---|
| Date | 2014-01-06 11:09 +1100 |
| Subject | Re: "More About Unicode in Python 2 and 3" |
| From | Chris Angelico <rosuav@gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.4989.1388966951.18130.python-list@python.org> (permalink) |
On Mon, Jan 6, 2014 at 10:45 AM, Ethan Furman <ethan@stoneleaf.us> wrote: > On 01/05/2014 03:31 PM, Emile van Sebille wrote: >> >> On 01/05/2014 02:32 PM, Serhiy Storchaka wrote: >>> >>> I wonder why nobody complains about the absent of implicit conversion >>> between int and str. In PHP you can write 2 + "3" and got 5, but in >>> Python this is an error. So sad! >> >> I'd want my implicit conversion of 2 + '3' to get '23' > > Huh. And here I thought 'twenty-three' was the right answer! ;) I quite like 2+"3" being "23", as it simplifies a lot of string manipulation. But there's another option: 2+"3456" could be "56". That one makes even more sense... doesn't it? I mean, C does it so it must make sense... ChrisA
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: "More About Unicode in Python 2 and 3" Chris Angelico <rosuav@gmail.com> - 2014-01-06 11:09 +1100
csiph-web