-
ubelt
A Python utility library with a stdlib like feel and extra batteries. Paths, Progress, Dicts, Downloads, Caching, Hashing: ubelt makes it easy!
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
ordered-set
A mutable set that remembers the order of its entries. One of Python's missing data types.
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.
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.
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.