Bad things about python

ITT we list all the bad things about python.

I know it has good points as well but thats not for this thread. thanks.

__Python is flawless__

Memory usage
OpenSSL support (not really related to the language itself)

whitespace as syntax is gay as fuck

>>1
- No multiline lambdas or expression def.

- Ifs, loops, etc., and more generally, blocks should be expressions that return the value of the last sentence.

- Closures are limited, not because they internally are, but because when you do x = 2, you immediately create a new reference x, not changing the one from an outer scope. This is a tradeoff; it doesn't happen in JavaScript, but on the other side, Python doesn't have dangerous automatic globals and it doesn't require you to define your variables. Still, I would like to have some kind of "outer scope" resolution operator.

- I would like to have C-like assignment operators and ++ --

- Modules should have been regular namespaces, working just like classes and functions.

- Regular expressions from the re module aren't as good as Perl's. They lack the experimental features.

- The re module needs simplification. You can fix it easily though.

Everything else looks great to me. It's overall my favourite language.

>>4
No. Already discussed. Not gay.

>>4
stfu, forced indentation is good.

python sucks because the interpreter is written in c

>>6
forced anything is for noobs, and I'm not a noob, therefore it sucks, the end.

>>8
seconded.

>>8
no, you're more likely a little curly-brace loving cunt lacking the mental capacity to accept anything unfamiliar

>>10
seconded.

>>10
lol.. my primary language is haskell, and ive used lisp a lot as well.

>>12
you expect anyone to believe that?

>>13
he thinks we will trust his crap as long as he doesn't post some code (the only Lisp code he ever wrote was Hello, world)

>>13
>>14
both wrong

This thread went bonkers fast. Are the things that >>5 really the only problems with Python?

My powerlevel isn't high enough to really understand any of the problems listed, so I'll just continue using Python and learning C at the side.

>>16
Make sure you learn memory management well.  Any application where performance is important will require a language that allows directly manipulation of how things are stored and accessed in memory.

>>13
>>15
>>14
all the same person, can you believe this guy? hes fuckin nuts

>>1
why dont you go back and script some php?
tard.

>>16
Personally, I don't like self, __, or things like len() either.

>>20
me neither, its evil

>>19
lol @ getting all anoyed about your favorite programming language FAGOT>>20

lol @ getting all anoyed about my favorite programming language php
fixd

>>1
Attack its weak point, for massive damage.

At least Python has real-time datatype change and is based on functional programming history. Being based on functional programming, the features of the language will also be based on actual features which took actually took place in Lisp. So here's this giant one-line lambda.

* poor performance
* Idiot creator
* Maintained by people who are similar to those who maintain PHP
* Wrong mix of features
* Bad operator overloading in the stdlib

One word, forced indenting

That's two words.

>>26

SHUT UP NO IT'S NOT I'M TELLING.

>>25
>>27
Not same

What i think >>25 was saying was making fun at how in python, "forced indenting" would become one word due to forced indenting. So it's like, satire.

>>29
You don't know what 'indenting' means, do you?

>>24
I think you hit the nail on the head pretty much exactly, these are the major problems and far outweight any of the (few) good things. imo.

>>30
You're an idiot.

def foo(a)
    forced indent

>>24
poor performance
Where? It outperforms Perl, Ruby and PHP. It's the fastest in its class, at least out of the popular ones.

idiot creator
Ok, do better.

Maintained by people who are similar to those who maintain PHP
That's why the standard library is so good?

Wrong mix of features
You can say something is missing (multi-fucking-line lambdas), but wrong mix?

Bad operator overloading in the stdlib
You * 0


>>25
No


>>31
gb2/"&)/(#&/()$&"=#)(/="&())#.

More interesting problems were posted in >>5, such as the way scopes are handled in closures or functional and declarative programming features, and what does >>24 have to say? Wah wah wah stupid map bad team lag wah wah wah.

Python is not perfect, but saying stupid things outweight the "few" good things, you're just trolling. And IHBT. Dammit.

>>26
"forced" is only one word.
the "indenting" part isn't bad, just the "forced" part.

>>33
makes arguments a bit like a primary school child.

>>35
>>5 was mine too. I just adapt to the poster I'm replying to.

>>34
That's like saying that forced semicolons at the end of lines is bad, or forced braces.

God dammit C++ sucks because it forces you to use [] for arrays and doesn't allow you to use %% in the sense that you cannot say howdy%1% = 1; instead you have to say howdy[1] = 1;

FUCK ALL LANGUAGES EXCEPT PYTHON AND WEEABOOESE

That's like saying that forced semicolons at the end of lines is bad, or forced braces.

so true!

>>38
The best programming language
is natural language
it's not forced anything

>>38
so FALSE