Sunday, September 19, 2010

Understand human behavior

Enhance your life





============================================================================================================================ ItÂ's tempting to say, we should use the original English, which is British English. Some suggest the original English remained in Britain when the North American colonies were founded; others claim it was brought to the Americas by the British settlers , leaving a pale imitation back in Britain. The truth is much stranger: the original English was actually smuggled out of Britain to the West Indies in a wardrobe belonging to General Sir Ralph Abercromby, where it ended up on the island of Trinidad after Sir Ralph took possession of that territory in the name of the British Crown. It came to be used and modified freely by the various immigrants to Trinidad (and later Tobago) and their descendants (largely African, Indian, British, Portuguese, German, Spanish, and Chinese). Many of these peoples then emigrated, bringing the original English to North America and back to Britain. A copy of it has fallen into my hands, and so I can, without bias, make the following call: both color and colour shall be acceptable in Haskell programming. 'Kerb' and 'gaol' are right out, however. Cheers, Robert (who's grandfather is from London and grandmother from Trinidad; but is nevertheless American) _______________________________________________ Haskell-Cafe mailing list Hask ... @haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe New submission from Jeremy Banks < jer ... @jeremybanks.ca >: It would be convenient if it were possible to divide one datetime.timedelta object by another to determine their relative durations. Were the datetime module pure Python a crude solution would just be to add two methods like this: def toMicroseconds(self): return ((self.days * 24 * 60) + self.seconds * 1000000) + self.microseconds def __truediv__(self, other): return self.toMicroseconds() / other.toMicroseconds() However, I don't understand know the Python C API well enough to know how to patch the C module. ---------- components: Library (Lib) messages: 75670 nosy: Jeremy Banks severity: normal status: open title: Allow Division of datetime.timedelta Objects type: feature request _______________________________________ Python tracker < rep ... @bugs.python.org > < http://bugs.python.org/issue4291 > _______________________________________ _______________________________________________ New-bugs-announce mailing list New- ... @python.org http://mail.python.org/mailman/listinfo/new-bugs-announce Hi, Bram, Another oddity I've recently discovered is that str2nr won't accept an explicitly positive number, such as '+3'. This is unexpected. Would you be willing to adjust the behaviour? I can't think of any negative/compatibility-breaking side effects this would have, but I also don't know where the vim_str2nr function is used. The attached patch does the job. Cheers, Ben. diff -r 64942db7407d src/charset.c --- a/src/charset.c Sat Jun 21 23:24:54 2008 +1000 +++ b/src/charset.c Tue Jun 24 03:24:33 2008 +1000 @@ -1799,6 +1799,7 @@ unsigned long un = 0; int n; + if (ptr[0] == '+') ++ptr; if (ptr[0] == '-') { negative = TRUE;