Gosh, and all I'm upset about is the need to put colons after statements when they're clearly not needed. More seriously, when I work with Python, I constantly

Gosh, and all I'm upset about is the need to put colons after statements when they're clearly not needed. More seriously, when I work with Python, I constantly have this vague feeling of mild frustration. I think it's because of all the oddball library stuff, issues with autocomplete in my IDE (I know I should find something better), idiomatic Python ways that seem to short circuit my brain's parser, I'm pretty much googling for almost every line I write. But then, after a few minutes, I look at what I've made and this weird wave of productivity washes most of it away and I'm surprised at what I just created. Recently I tried to rewrite a personal Java project in Python. I had hacked away at the Java project in my spare time for weeks. The Python version took me about 10 hours over two days, that included hunting down and installing all the libraries. I do agree that cross-platform support isn't what it should be, and there's a surprising number of times where the Python library is just a wrapper around a command-line executable (which of course only builds on Linux or Windows or whatever). There's also an alarming number of old libraries which have long since been deprecated, but the internet is awash in the former library's popularity and it's much harder to find information on the supposed replacement. More importantly, nobody really bothers to tell you "don't use the old and busted one, use the new hotness". You just sort of have to figure it out because pip doesn't have it or something. I'd also love a Python version of Perl's -c which sort of pseudo-compile-time checks your code without running it.