best-of-generator VS ubelt

btw. If you like to keep track on how we might implement your suggestion, you can also open an issue here with your suggestions: https://github.com/best-of-lists/best-of-generator/issues/new/choose

Good point. Our goal is actually to get to an automated scoring system that can reflect not just popularity, but also lots of other qualitative factors for libraries. With our initial release, we are already taking many different factors into account, not only stars: https://github.com/best-of-lists/best-of-generator#project-quality-score . But there is a lot to improve, and we are working on an improved version of the calculation.

Welcome to the post about the Top 5 Python ML Model Interpretability libraries! You ask yourself how we selected the libraries? Well, we took them from our Best of Machine Learning with Python list. All libraries on this best-of list are automatically ranked by a quality score based on a variety of metrics, such as GitHub stars, code activity, used license and other factors. You can find more details in the best-of-generator repo.

I can't give you a stdlib, but I can give you a package with a lot of the basic functionality but still small enough that it installs quickly and has negligable overhead. The ubelt library is a set of 100ish utility functions and classes. It's similar to boltons, but I suppose it reflects a different perspective on what's useful.

Number 3 is the one I feel most conflicted about. Specifically, I tout my ubelt library as having 0 required dependencies. However, it vendors two libraries: progiter and orderedset. The first of which I also maintain and the second of which I don't maintain, but have contributed to. It feels odd to have a single dependency for a library that would otherwise have zero. But at the same time it feels odd to maintain that code myself. Also if I didn't vendor it, it would not be included in the documentation, so there is that. I've recently been thinking I should split ubelt up into many smaller packages and then use ubelt as a "hub" to include them all. However, that's a lot more work than just maintaining one (still quite small) package, and I think having everything broken up with incur a lot of overhead at pip install time, so I'm very conflicted on the whole subject.

I'm fairly happy with my ubelt library.

The ubelt.util_platform module is a good example of including references to similar functionality.

I also have a utility library ubelt with 552 stars and 6.9k downloads / month.