Log file Viewer

[18:35:51] <exarkun> How do I inspect the ownership history/audit log for a project I don't own/admin on pypi?

[18:36:59] <sumanah> hi exarkun -- I believe that's not currently possible. https://github.com/pypa/warehouse/issues/5863 we're working on it

[18:37:38] <sumanah> exarkun: as you probably already know, release history is available to the public at, e.g., https://pypi.org/project/arrow/#history

[18:38:09] <exarkun> indeed. there's no information visible about who made/uploaded the release though, right?

[18:43:01] <sumanah> exarkun: Right now there is not

[18:43:14] <exarkun> okay. thanks.

[18:43:23] <sumanah> exarkun: you can subscribe to issue #5863 for updates on the work

[18:43:31] <sumanah> it'll be in the next few months

[18:44:11] <sumanah> exarkun: https://github.com/pypa/warehouse/issues/5864 is something where we could use your input btw

[18:53:57] <ngoldbaum> exarkun: if this is something you need to do and need help with, I guess you could find who tagged the commits in the repository? ofc tagging and uploading the release are disjoint.

[18:55:24] <exarkun> I'm looking at pyutil specifically. It has a different owner than I expect. The latest metadata points at a different github repo than I expected. I'm curious if the ownership was ever what I thought it would be and if so, when this changed.

[18:55:46] <exarkun> In this case, I don't even know which repo any tags that might correspond to uploads would be in.

[18:56:45] <exarkun> It's almost certainly a misunderstanding on my part but it would be nice for me if I could see a history of ownership and upload responsibility.

[18:57:09] <ngoldbaum> https://pypi.org/project/pyutil/ ?

[18:57:25] <ngoldbaum> darcs wow

[18:57:57] <ngoldbaum> issue tracker hasn't been touched since 2015

[18:58:41] <ngoldbaum> i guess this is the repo? https://github.com/zooko/pyutil

[18:59:06] <ngoldbaum> certainly not for the recent releases though

[18:59:10] <exarkun> I dunno. Or https://github.com/tpltnt/pyutil ?

[18:59:25] <exarkun> Note the homepage link from pypi is https://github.com/tpltnt/pyutilpyutil

[18:59:41] <ngoldbaum> yeah, this is the maintained fork: https://github.com/tpltnt/pyutil

[19:30:40] <exarkun> on a more or less unrelated topic

[19:31:15] <exarkun> how do I discover why "setup virtualenv" on https://circleci.com/gh/tahoe-lafs/tahoe-lafs/9385 is 3m faster than that step on https://circleci.com/gh/tahoe-lafs/tahoe-lafs/9648

[19:32:55] <exarkun> maybe it's a tox question, dunno

[21:25:37] <tos9> exarkun: I don't know what setup virtualenv is or does

[21:25:47] <tos9> But the one "obvious" thing that's always worth checking is

[21:25:52] <tos9> The crazy "copy current working directory" behavior

[21:26:05] <tos9> So possibly your 3s is copying a large cwd in one of thsoe two repos.

[21:27:17] <ngoldbaum> i think virtualenv will copy the entire .tox directory if it exists?

[21:27:38] <ngoldbaum> which might be very large if your dependency graph has large dependencies or if you have a big build matrix

[21:31:06] <exarkun> tos9: it's the same repo

[21:31:38] <exarkun> so same dependencies and such

[21:35:59] <tos9> exarkun: is it literally the same directory though

[21:36:04] <tos9> e.g. one way you will have a bad time is

[21:36:20] <tos9> job 1 executes, creates giant .tox folder, then job 2 operates on same working directory, and now copies giant .tox directory as part of `pip install`

[21:36:34] <tos9> (uselessly, because that directory isn't part of the install at all)

[21:54:31] <exarkun> tos9: no they're independent CI runs

[21:54:53] <exarkun> the obvious difference is that one is cpython and the other is a brand new pypy config I'm trying to add

[23:38:55] <exarkun> it had something to do with how the wheelhouse was populated, so it was being ignored

[23:39:47] <exarkun> next. why does pyutil end up like `file:///tmp/wheelhouse/pyutil-0%2Bunknown-py2-none-any.whl` in the wheelhouse when I `pip wheel https://github.com/exarkun/pyutil/archive/pypy.zip#egg=pyutil`?