Python is an object oriented programming language, not a "scripting" language. "Scripting" implies writing "scripts" (e.g. #!/usr/bin/python), but that's not i

Python is an object oriented programming language, not a "scripting" language. "Scripting" implies writing "scripts" (e.g. #!/usr/bin/python), but that's not it's only (or primary) use case, and in fact creates the problems I've been talking about above. Python the language has plenty of flaws. This conversation was never about Python however, it was about the bad habits C programmers bring to Python enterprise development, and how I struggle to work with C programmers because of those good-in-c-but-bad-in-python habits. I was curious if anyone else experienced these problems, and then you arrived and became a perfect example of the attitudes I encounter regularly from C programmers working in Python. I have no problems with C, it's obviously one of the most (if not the most) important programming languages of our time. My problem is with the habits some C programmers have brought to my Python projects.