[01:08:09] <donald> Traceback (most recent call last): File "/usr/bin/pip3", line 9, in <module> from pip import main ImportError: cannot import name 'main'
[01:08:09] <donald> are you sure nothing is broken?
[01:21:11] <techalchemy> not really, it's hard to say exactly waht is going on, wish I had more time to help but I have to take care of a few things unfortunately
[01:21:28] <techalchemy> there is some good info about these kinds of things online, especially for debian because they make it very easy to screw this up
[01:51:58] <donald> https://paste.debian.net/1029634/ since I did pip install x; with not --user I can not download any package anymore
[02:30:12] <feuli> since I have done $pip install --upgrade git+https://github.com/arthaud/python3-pwntools.git --userCollecting git+https://github.com/arthaud/python3-pwntools.git I have: https://paste.debian.net/1029634/
[19:37:59] <dwighthubbard> I have a question. I have the new bandersnatch 3.0.0dev running in staging environments on the west coast and the midwest with a wrapper that is storage the sync runtime and serial numbers of each run.
[19:39:50] <dwighthubbard> I'm noticing between 5:30-8:30am PST that the mirror sync on the west coast is taking significantly longer.
[19:40:39] <dwighthubbard> I'm wondering if this is due to some known pypi/fastly configuration or if I need to dig into into my infrastructure side a bit more.
[19:49:33] <cooperlees> dwighthubbard: Is it only during that time every day?
[22:42:18] <dwighthubbard> I see the sync runtimes increase in both data centers about that time every day, but generally the runtime from the west cost is around twice as long as the midwest datacenter.