On Tue, 3 Oct 2017 10:13:53 -0600
Chris Barker
On Tue, Oct 3, 2017 at 5:22 AM, Antoine Pitrou
wrote: Daniel Stutzbach's blist is well-known at this point: http://stutzbachenterprises.com/performance-blist https://mail.python.org/pipermail/python-ideas/2014-September/029434.html
https://mail.python.org/pipermail/python-ideas/2014-September/029434.html (inconclusive)
that was some years ago -- I wonder how much use it's seen?
You can go a surprisingly long way with Python's built-in and stdlib containers, so I'm not surprised it's not very widely used.
but I note:
"I'm really reluctant to include `blist` as a dependency, given that it would basically mean my package wouldn't be pip-installable on Windows machines. "
With binary wheels and all, this isn't the same issue it used to be -- so a third party package is more viable.
I don't know what wheels are supposed to change here. You could already build binary packages for Windows before wheels existed. The problem as I understand it is that you need a Windows machine (or VM) together with the required set of compilers, and have to take the time to run the builds. With conda-forge though, one could simply submit a recipe and have all builds done automatically in the cloud. Your users then have to use conda (rather than pip and virtualenv). Regards Antoine.