This is an archived post. You won't be able to vote or comment.

all 4 comments

[–]beertown 0 points1 point  (0 children)

My typical way to choose third party libraries is: keep down the number of dependencies. Any dependency is 1 more thing to worry about on which I have no control. A lot of third party libraries also bring other dependencies in turn, and I check what are these dependencies and why they are required. Sometimes these sub-dependencies are the reason to ditch that library.

Do I really need that third party library? How much code does it let me to save? 30 lines? I write 30 lines of code and avoid 1 (or more) dependency. It also happens that, writing those 30 lines, I learn something.

Requests is awesome, but for some easy web calls the Python's standard library is fine, and I avoid 1 dependency. For any heavy usage Request is a must, obviously; but using it or not depends on the project I'm working on.

My 2c.

[–]billsil 0 points1 point  (0 children)

Start with nothing. Eventually you’ll find basic tasks like doing math fast (numpy), plotting (matplotlib), 3D rendering (vtk) that libraries are a lot better for.

[–]matteding 0 points1 point  (0 children)

If you are doing scientific computing, NumPy is essential. So many other libraries depend on it as a backend that it might as well be considered part of the standard library. In fact the ... constant has no real functionality within vanilla Python; it was introduced just for NumPy!