Re: computing with characters

On Apr 30, 6:47 am, Duncan Booth <duncan.bo...@xxxxxxxxxxxxxxx> wrote:
Torsten Bronger <bron...@xxxxxxxxxxxxxxxxxxxxx> wrote:
The biggest ugliness though is ",".join(). No idea why this should
be better than join(list, separator=" "). Besides, ",".join(u"x")
yields an unicode object. This is confusing (but will probably go
away with Python 3).

It is only ugly because you aren't used to seeing method calls on string
literals.

I'm used to seeing it and I think it's ugly. Too terribly convenient
to not use, though (which is why I'm used to seeing it).


Carl Banks
.

Relevant Pages

  • Re: computing with characters
    ... yields an unicode object. ... This is confusing (but will probably go ... away with Python 3). ...
    (comp.lang.python)
  • Re: computing with characters
    ... yields an unicode object. ... This is confusing (but will probably go ... away with Python 3). ... rather administrative operation on strings (and actually ...
    (comp.lang.python)
  • Re: Variables with cross-module usage
    ... In Python, it easy, perhaps too easy, to rebind built-in names, but it is usually a mistake. ... name can be used to refer to multiple objects just by context without referring any namespace. ... Silicon is a part of the natural world, and I was not making any such analogy. ... Dennis clained that Python is confusing because it is not restricted to naming locations. ...
    (comp.lang.python)
  • Re: Unicode Hell
    ... I suppose Requestis a Unicode object, ... trying to do here is a brute force conversion to a normal Python ... What you could do is convert the Unicode object to a Python string, ... FileContents string. ...
    (comp.lang.python)
  • Re: [Info] PEP 308 accepted - new conditional expressions
    ... including python (if Condition: ... I've always found C's order confusing, ... The whole idea of a ternary operator is somewhat complex. ... though reading other's code is usually simpler. ...
    (comp.lang.python)