11 ms·
> It's one of the biggest reasons not to use Python IMO. No other popular language has this issue. No other popular language struggles with issues of backwards
by davesque 9y ago
> It's one of the biggest reasons not to use Python IMO. No other popular language has this issue.
No other popular language struggles with issues of backwards incompatibility? That's a huge exaggeration.
> Difficult to distribute standalone programs. You end up having to bundle an interpreter which is a pain.
I guess then you generally prefer not to use interpreted languages?
> So many programs include python interpreters you end up with insane path issues...
How is that? There's usually a system Python which system programs should reference explicitly if they care. If you code up a Python program without being careful about its dependencies, then yeah you're asking for trouble. But that's true of any program, whether it needs to locate an interpreter or be compiled against a shared library.
None of the pain points you mention are inherently specific to Python. But maybe Python's huge success and ubiquity trick people into conflating general software development issues with Python issues; rather like how people start confusing popular brand names with actual products (e.g. Band-Aids).
- IshKebab 9y ago> No other popular language struggles with issues of backwards incompatibility? That's a huge exaggeration. Pretty much true. As far as I know C, C++, Java, C#, Javascript, etc. have never broken backwards compatibility. At least not in a serious way (like changing how `print` works). > There's usually a system Python which system programs should reference explicitly if they care. Not on Windows.