[20:51:17] <Yasumoto> wickman is the man with the plan, but I'm a decent starting point
[20:51:46] <dstufft> Yasumoto: if I pex up something that depends on say, psycopg2. Will pex bundle libpq.so as well, or will it still depend on libpq.so to be installed on the system
[20:52:00] <Yasumoto> it will still need that native lib on the system
[21:01:31] <lifeless> dstufft: so I have this draft pep to move forward on getting that lib installed
[21:08:32] <dstufft> lifeless: I haven't even begun to read that PEP :( I probably should at some point
[21:08:49] <lifeless> dstufft: I have a raft of edits planned
[21:08:56] <lifeless> dstufft: been so fragmented these last weeks
[21:09:05] <dstufft> sounds like I should wait downstream then
[21:20:25] <ErikRose> dstufft: Any better ideas for a name for the hash-checking mode? "Secure Mode" has too much overlap with other security features, like HTTPS cert checking. "Hash-checking mode" is more accurate but long.
[21:22:34] <dstufft> does it need a short name (or a name at all really)? Do we expect people to interact with the name at all? AFAIK the proposal is that if you hash a hash then all must be hashed, but thre's no flags or anything like that?
[21:22:42] <dstufft> I mean there's like --sha256 or whatever
[21:22:52] <dstufft> but there's no flag to explicitly enable it
[21:23:29] <ErikRose> I'm just naming vars for now. Just wondered if you had an obvious one.
[21:23:50] <ErikRose> The only exposure I see in the future would be a CLI flag, and --ignore-hashes is fine for that.
[21:34:35] <xafer> dstufft, https://github.com/pypa/pip/pull/3085 seems ok to me but I'm wondering about the tests: we were testing "pip install --download..." and with this PR we will only test "pip download ...". Shouldnt we test both calls during the deprecation period ?
[21:40:48] <dstufft> xafer: um, IDK. We generally don't test deprecated stuff but maybe we should here