Re: Real-world use cases for map's None fill-in feature?

2006-01-24 Thread Andrae Muys
and one *wrong*. Just that one is at least slightly better than the other; or even that one was chosen simply because either was better than neither. API design decisions are not personal vendettas against your use-case :). Andrae Muys -- http://mail.python.org/mailman/listinfo/python-list

Re: Real-world use cases for map's None fill-in feature?

2006-01-23 Thread Andrae Muys
instead of a padding zip leads to an incorrect result. 3. Using a padding zip instead of a truncating zip leads to non-termination. 4. A terminating bug is preferred to a non-terminating bug. Hence zip is generally truncating. Andrae Muys -- http://mail.python.org/mailman/listinfo/python-list

Re: Real-world use cases for map's None fill-in feature?

2006-01-22 Thread Andrae Muys
in the domain of iter1 or iter2 as a fence, but a closure is guarrenteed to satisfy that requirement and hence keeps the code generic. In the padding example, if you actually care what value is used for pad then either you can either replace fence, or wrap the result in an imap. Andrae Muys -- http://mail.python.org/mailman/listinfo/python-list