[Python-ideas] The non-obvious nature of str.join (was Re: sum(...) limitation)
Alexander Belopolsky
alexander.belopolsky at gmail.com
Mon Aug 11 15:56:38 CEST 2014
More information about the Python-ideas mailing list
Mon Aug 11 15:56:38 CEST 2014
- Previous message: [Python-ideas] The non-obvious nature of str.join (was Re: sum(...) limitation)
- Next message: [Python-ideas] The non-obvious nature of str.join (was Re: sum(...) limitation)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Aug 11, 2014 at 2:56 AM, Wolfgang Maier < wolfgang.maier at biologie.uni-freiburg.de> wrote: > I am using Python for teaching programming to absolute beginners at > university and, in my experience, joiner.join is never a big hurdle. In my experience, it is the asymmetry between x.join(y) and x.split(y) which causes most of the confusion. In x.join(y), x is the separator and y is the data being joined, but in x.split(y), it is the other way around. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-ideas/attachments/20140811/ad4f4728/attachment.html>
- Previous message: [Python-ideas] The non-obvious nature of str.join (was Re: sum(...) limitation)
- Next message: [Python-ideas] The non-obvious nature of str.join (was Re: sum(...) limitation)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-ideas mailing list