3 ms·
I won't bother with Python again because these conflicts happen on your first time even trying out the language. (running linux, any better on Windows?) It was
by RobertRoberts 7y ago
I won't bother with Python again because these conflicts happen on your first time even trying out the language. (running linux, any better on Windows?)
It was such a mess that I can't even describe the frustration. And I even got Apache working with SVN! (40 pages of docs and no testing points from start till it's fully working, yuck)
EDIT: Since I got downvotes so quick, tell me why anyone should choose Python over the many alternative out now?
- joshklein 7y agoThere’s too much to untangle for a brief explanation, but if this really happened when you tried writing Python on Linux for the first time, or using a program written in Python you installed through your distribution’s package manager, file a bug report with your distribution.
- RobertRoberts 7y agoIt wasn't "bugs" it was all the hoops to jump through, conflicting hoops, multiple installed versions, pip vs all the other package installers, that also caused conflicts, etc... Since I am not a Python dev, I would be unable to provide a useful report even if it were bugs.
- nurettin 7y agoSorry you went through the trouble of what is called "setting up a development environment" and yes, I wish you could simply start coding and distributing programs as soon as you boot up a computer, but that is simply not the case anymore. Not with python, not with ruby and not with go.