Improving Your Python Productivity(ozkatz.github.com)
ozkatz.github.com
Improving Your Python Productivity
http://ozkatz.github.com/improving-your-python-productivity.html
8 comments
One single productivity python I'd like to share here is to use 'string foo'.partition(' ') instead of splitting. The reason is the edge cases are better handled with partition: you always get a 3-tuple, no matter what. No need to precheck that the split is here, or to postcheck the length of the splitted list.
On the other hand, .split() with no argument splits on any amount of whitespace (\s+, as a regex). That's often quite a useful edge case to have handled for you. You can also do .split(c, 1) to limit it to a single split. It could still split 0 times, though - it just depends which edge cases you want to handle.
After reading a few comments here I'm surprised there's no "Effective Python" book already (given the age of Python itself).
In Java and .NET, that's what we try to do everyday: writing idiomatic Java/C# code (style, architecture, patterns, standard libs, etc).
In Java and .NET, that's what we try to do everyday: writing idiomatic Java/C# code (style, architecture, patterns, standard libs, etc).
Though I have yet to come across book titled "Effective Python", books like "Python Essential Reference" by David Beazly and "Python Cook Book" covers lot of ares that you mention above.
I was hoping to find some mention of IDE, IDE plugin, or more process oriented stuff, rather than language features.
Not a very helpful article. Far from a general "improve your Python productivty", it's more like "here are some minor random Python features that I think are useful".
TLDR:
* Use dict and set comprehensions.
* Use collections.Counter.
* Use json.dumps or the pprint module for pretty printing.
* Create simple web services with Python's XML-RPC library.
* Use open source libraries...
TLDR:
* Use dict and set comprehensions.
* Use collections.Counter.
* Use json.dumps or the pprint module for pretty printing.
* Create simple web services with Python's XML-RPC library.
* Use open source libraries...
As we move toward languages with big standard libraries, productivity becomes more and more about knowing what you don't have to do yourself.
Case in point - even as a Python veteran, I've never seen/used collections.Counter before. It'll save me from writing the same stupid three lines over and over, and is probably implemented faster than I naively do. I'd say that this will improve my productivity.
Case in point - even as a Python veteran, I've never seen/used collections.Counter before. It'll save me from writing the same stupid three lines over and over, and is probably implemented faster than I naively do. I'd say that this will improve my productivity.
Could not agree with you more. The more advanced I become with a language, the more I like to go back to even basic docs and read the small-print fancy uses for built-ins. This article touches on a number of them, and it's tricks like this that help you write better code (when used responsibly, of course).
Usually collections.defaultdict is faster than collections.Counter. But the latter is more concise to use.
The biggest problem is having to use old LTS distros in production that only have python 2.6 for example. I'm glad that most LTS versions are soon to be using python 2.7.
I know 2.7 has been around for a long time, but so much production software is running on RHEL/Centos systems with 2.6.
I know 2.7 has been around for a long time, but so much production software is running on RHEL/Centos systems with 2.6.
To make you feel a bit better - some of us are still on RHEL 5 and Python 2.4. Yes it is painful.
You can find python26 in EPEL [1] or follow this guide [2] to setup 2.7. This will install 2.6 or 2.7 in parallel, do not set these by default as it will break yum.
[1] https://fedoraproject.org/wiki/Python26
[2] http://villaroad.com/2010/10/rolling-python-2-6-2-on-centos-...
[1] https://fedoraproject.org/wiki/Python26
[2] http://villaroad.com/2010/10/rolling-python-2-6-2-on-centos-...
tl;dr: know the stdlib and the ecosystem well.
yep, my sentiments exactly. nothing at all having to do with productivity.
Whitespace as syntax? Really?
Yes really. If you have any further questions about the python language specification, you can answer them here: http://docs.python.org/3/reference/
Flashnews:mostmodernlanguagesdoindeedusewhitespaceassyntax.
Here's a good explanation about whitespace in Python http://www.secnetix.de/olli/Python/block_indentation.hawk
Have you never seen python before?
It's more likely than you think.
Let's call it canonical offside rule.
Despite the negative comments here, it's always good to be reminded of some of nice built-in things.
Reminds me how awesome pythons standard functionality really is.
[deleted]