[01:06:01] <dstufft> Is there anyone in here who happens to be familar with zc.buildout? aclark I think? ;)
[03:22:52] <jaraco> I've got this issue with pyvenv - http://paste.jaraco.com/DFTHx
[03:24:08] <jaraco> I'm getting inconsistent results depending on if the env is 'activated' or not when a package is install. Yet, the activation script does little but update the PATH and VIRTUAL_ENV vars.
[03:24:30] <jaraco> And I can't tell where the issue lies or where I can report it.
[03:24:50] <jaraco> I can work around the issue by not using the activation script, but I'd like to file a report and link to it if possible.
[03:24:57] <jaraco> (unless one is already filed).
[03:25:31] <jaraco> I'm just not sure if this is an issue with Debian or pip or pyvenv (or other).
[04:36:42] <Alex_Gaynor> jezdez: not sure if there's anythign to be done, but https://caniusepython3.com/check/54fc9192-b6af-47e2-8c32-c5a700e07f14 has been spinning for likw 5 minutes
[09:54:08] <jezdez> Alex_Gaynor: yeah, it's a bummer, the queuing system doesn't behave the same since I moved to heroku. gonna switch to rq that should speed things up
[13:26:17] <dhellmann> Ivo: yes, if we install oslo.config with "pip install" and oslo.messaging with "pip install -e" then "from oslo.config import cfg" fails with a message indicating that the config sub-package can't be found at all
[13:28:45] <dhellmann> dstufft: yes, I think that case is at least similar to what we were seeing
[13:29:15] <dhellmann> dstufft: my description above may be remembering the order of installation backwards, or it may not matter which order things are installed