Hacker News Reader

It's nice to have as small dependencies as possible. If Pint provides everything your project needs, buying into the complete Sympy ecosystem is just a complexity cost.

View on HN

Having used sympy for rather simple task I wonder how much cost sympy really adds. Can you elaborate? It seems to me that symbolic evaluation and unit conversuin are not too far apart and buying into this ecosystem was never a big tech debt in my eyes. (Unlike maybe scipy or numpy)

Every dependency adds complexity to your project, you might never notice it because the abstractions are water tight (for your use-case) but it’s there.

Yes but pint seems to add numpy and dask from a quick check. How is sympy worse? And maintaining sth yourself for sure adds complexity.

From the documentation:

Dependency free: it depends only on Python and its standard library. It interacts with other packages like numpy and uncertainties if they are installed

Oh I guess I looked into some build dependencies because there were actually none . This is actually a good thing more libraries should do. So I guess the only downside would be that potentially versioned dependencies/breaking changes need to be managed one level above if you want to use those parts. Is there actually a good way manage "supported" optional dependencies in python?

Reply on news.ycombinator.com