Re:Hidden features of Python
by omaranto on Wednesday July 14, 2010 @08:07PM
(#1516397)
map-comprehension is a bad name for that function, since it doesn't give you comprehension-like syntax, instead it is just a function that behaves like map but produces a map instead of another sequence. I'd call it map-map.
Re:Hidden features of Python
by mccutchen on Tuesday July 13, 2010 @11:44PM
(#1513531)
This is just a side-effect of bool being a subclass of int and True and False having the values 1 and 0, respectively. It might seem weird or surprising, but it's not a problem with Python's type system.
Re:Hidden features of Python
by cma on Tuesday July 13, 2010 @09:22PM
(#1513284)
When is it ever desirable? I'm open to it having a use, but I don't see one. The only thing I've gotten from it is mismatched types that made it past some unit tests but blew up in the real world.
Re:Hidden features of Python
by RodgerTheGreat on Tuesday July 13, 2010 @10:00PM
(#1513347)
I was making a glib joke, but to answer your question this is the tradeoff of using a not-so-strongly-typed language. Weakly-typed languages often save you some typing (if you'll forgive the pun) and implicitly convert in ways that can make it difficult to prevent those mistakes.
It's just like Duck Typing- you're trading the need to explicitly specify an interface for the potential dangers of letting your interpreter "know what you mean".
If this is frequently a problem, well... there are a lot of strongly-typed languages out there waiting for you to give them a try.
Re:Hidden features of Python
by masklinn on Wednesday July 14, 2010 @07:27AM
(#1514253)
In fact, to expand on the latter part of my comment, "weak typing" is generally understood as implying implicit type coercions or conversions at runtime. PHP and Javascript famously convert between numbers and strings depending on a bunch of factors (and usually the wrong way leading to unreliable results).
In that sense, Python is a very strongly typed language: from the top of my head, the only example of implicit type conversion in Python is the promotion of `int` to `long`, which has been removed from 3.x (all integer types were unified). All other conversions have to be explicit as far as I remember. That makes Python more strongly (but less statically) typed than Java (see the very strange overloading of the `+` operator when any operand is a string, as well as autoboxing since 1.5) and C# (C# allows for implicit type conversions, including in userland, and the cast operator doubles up as an explicit type conversion operator which I find terrible)
Re:Hidden features of Python
by eru on Tuesday July 13, 2010 @11:15PM
(#1513491)
Python is fairly strongly typed in general. (At least compared to Perl and the like. Examples like True + True notwithstanding.) It is just also very dynamic.
Re:Hidden features of Python
by oddthink on Wednesday July 14, 2010 @10:44AM
(#1514687)
This is only tangentially related, but try looking up "Iverson brackets" and Knuth's "Two notes on notation". One argument there is that False - True = -1 makes sign(x) = [x > 0] - [x < 0], which is convenient. I don't know of a case where True + True = 2 helps, but maybe something involving dual sums would be relevant.
Re:Hidden features of Python
by cma on Thursday July 15, 2010 @04:41PM
(#1519104)
The Iverson Bracket would already exist in a python that didn't subclass bool from int; '[boolean_expression]' would be, in python notation: 'int(boolean_expression)'.
Sounds kinda like I'm making the same argument as Knuth in forcing '[]' over '()'.
Re:Hidden features of Python
by defun-fun on Wednesday July 14, 2010 @01:13AM
(#1513662)
The greatest hidden feature of Python (for me) was its standard library. Its sheer size and completeness, I should add.
Yes, I have heard of "batteries included" and all, but after working with Python for a year I still felt that the size of its library has been "hidden" from general programming public.
Re:Hidden features of Python
by cpprocket on Wednesday July 14, 2010 @01:16AM
(#1513667)
You can add the number of Python implementation to your list of "hidden" features as well: IronPython, CPython, Jython, PyPy, unladen-swallow, Python3 - and all of them are of pretty high quality!
Re:Hidden features of Python
by brlewis on Wednesday July 14, 2010 @11:11AM
(#1514794)
I feel validated that the chaining comparison operators feature is #1 in terms of votes (303 vs #2 at 249 as I write this). Nobody else seems to think it worth mentioning, but chaining comparison operators is a feature I'm really fond of in Lisp/Scheme: http://www.cs.cmu.edu/Groups/AI/html/cltl/clm/node124.html
Re:Hidden features of Python
by omaranto on Wednesday July 14, 2010 @08:09PM
(#1516406)
I wouldn't say Lisp has chaining of comparisons, only chaining of identical comparisons: a < b < c --> (< a b c), but a < b <= c --> (and (< a b) (<= b c))
You can check if two out of three are true with
(bool1 + bool2 + bool3) >= 2
You can do
count_negatives = sum(number < 0 for number in numbers)
It's just like Duck Typing- you're trading the need to explicitly specify an interface for the potential dangers of letting your interpreter "know what you mean".
If this is frequently a problem, well... there are a lot of strongly-typed languages out there waiting for you to give them a try.
Not in this case. In this case it results from:
1. Python historically not having booleans and using 0 and 1 instead
2. As a result, `bool` inherits from `int` for compatibility reasons
with False mapping to 0 and True to 1 for compatibility purposes 3. Add isn't overridden on bool therefore, when adding two booleans you're really adding two integers.Most non-strongly-typed languages will not have the following behavior
In that sense, Python is a very strongly typed language: from the top of my head, the only example of implicit type conversion in Python is the promotion of `int` to `long`, which has been removed from 3.x (all integer types were unified). All other conversions have to be explicit as far as I remember. That makes Python more strongly (but less statically) typed than Java (see the very strange overloading of the `+` operator when any operand is a string, as well as autoboxing since 1.5) and C# (C# allows for implicit type conversions, including in userland, and the cast operator doubles up as an explicit type conversion operator which I find terrible)
Sounds kinda like I'm making the same argument as Knuth in forcing '[]' over '()'.
So no, it does not have a use :)
Yes, I have heard of "batteries included" and all, but after working with Python for a year I still felt that the size of its library has been "hidden" from general programming public.
I love Python.
Runs a local SMTP server on port 2525. Very useful for debugging.
Now that's a feature I wish I knew about sooner. I've been using:
which has always felt kludgy.(Ok, I didn't know about re.DEBUG)
EDIT: I'm not claiming this link is worthless. But I'd call it "great features of python" or simply "features of python"