story
It only ever makes sense to use Python for data-science one-offs and munging if you have competency in Java/C#/etc. It's not a language well suited to application development.
Hopefully it changes now that C# is open source, but for now it's quite a big downside.
I don’t know if that is still true today.
Threads which start like that rarely end up contributing anything of value or convincing anyone who didn’t already agree with the author.
I work with Python every day and have for years and it's strengths and weaknesses are readily apparent to me but not to everyone apparently.
Since this is a Django thread, that could be covering things about, say, why you prefer .Net forms or trade offs from various ORMs.
I think C# is a quite respectable language so you could cover, say, why its typing is more productive than something like mypy or how package management compares.
Big nono!!
C# is a powerful language that is highly expressive, has a great type system, excellent compiler and great IDE, excellent async support, fast HTTP stack in standard library, blessed application development framework and object relational mapper, etc. Basically everything you could ask for in an ecosystem for developing a long-lived web application.
Python is a scripting language which is great for one-offs and has great data-science libraries but lacks static typing, poor IDE experience, slow runtime performance, poor portability because of it's reliance on FFI, poor long-term application maintenance track record, no blessed frameworks, competing and incompatible async solutions, etc.
Tbh I don't think there is much contest. Yes you can write a bunch of Python quickly that will do something but if you already know C# which is much better suited for the task it's clearly a better choice.
Maybe but you should always ask for what, that's the main-point. Sometimes Java or even Javascript/Node is the best stack. Many many point's play into a decision for a web-stack, maybe he wants that "quickly", maybe he works in a C# shop and so on....