12 Mar
2009
12 Mar
'09
9:48 p.m.
On Wed, Mar 11, 2009 at 19:55, Dieter Maurer <dieter@handshake.de> wrote:
The parameter was pointless in the first place. One and only one value for it worked -- the one that could be determined automatically.
Which is why it was removed. :) (and also, I think there was a use case where the one calling the parameter *didn't* know the value. Five I think. Ah well)
Thus, it was good to get rid of it -- just the deprecation warning was silly: instead, a value different from the only correct one should have resulted in an exception.
True. -- Lennart Regebro: Pythonista, Barista, Notsotrista. http://regebro.wordpress.com/ +33 661 58 14 64