[12:40:11] <apollo13> I was more like after a few requests a seconds
[12:40:48] <apollo13> we can handle quite a bit, but if you try to like fetch a few hundred package infos in one second for a long time, we might notice
[12:41:53] <BenediktE> Yep, that is clear. Just don't want to cause any trouble. That much packages are not yet needed.
[12:42:09] <Wooble> Trying to install them all on the same python installation might not prove they don't work; there could be conflicts.
[12:43:27] <BenediktE> I would programatically setup a new environment.
[12:43:49] <BenediktE> Hope this kind of "testing" will show up which packages work and which not
[12:44:03] <BenediktE> That they might crash later at use, is not tested with this
[12:44:37] <Wooble> ideally, run their test suites...
[12:44:57] <Wooble> This may be harder to automate :)
[12:52:16] <BenediktE> As far as I can see, using the search-method in combination with python_version is not possible, or am I wrong?
[19:45:08] <vin> I am trying to download the pip package docoptcfg using the direct link: https://pypi.python.org/packages/source/d/docoptcfg/docoptcfg-1.0.2.tar.gz. This 404's, same link works for other packages (for example daemonize, docopt)
[19:45:22] <vin> Can this be disabled on a per package basis?
[19:46:13] <dstufft> vin: https://github.com/pypa/pypi-legacy/issues/438 I suspect this