Log file Viewer

[01:23:43] <njs> cooperlees: EWDurbin was also talking about the idea of having like ~monthlyish pypa office hours / status chat

[01:28:58] <techalchemy> are API discussions happening somewhere ?

[01:29:11] <techalchemy> I definitely would love to provide some input

[01:30:17] <dstufft> techalchemy: there's an issue on warehouse atm

[01:30:27] <techalchemy> cool

[01:31:03] <techalchemy> I need to verify but I believe we are still using the XMLRPC resolver as a fallback resolver or something

[01:31:10] <dstufft> https://github.com/pypa/warehouse/issues/284

[01:31:41] <techalchemy> it catches edge cases, specifically I think we implemented it for a case where we needed to normalize a name that only had a post release

[01:31:48] <techalchemy> they had deleted the original release

[01:32:35] <dstufft> techalchemy: if there's use cases that only exist in the xmlrpc we def need to know those so we can either explicitly declare them unsupported, or support them.

[01:32:44] <njs> mbacchi: heh, I just wrote what sounds like it might have been the same script you're writing last week. https://gist.github.com/njsmith/f45b20aafbcbab4fe11c06fab588427a

[01:32:51] <techalchemy> yeah I need to verify, the package was ibm-db-sa-py3

[02:30:42] <altendky> techalchemy: is pipenv only testing on appveyor now? or is something going on on the phabricator instead of travis?

[02:36:25] <techalchemy> altendky: it's testing on buildkite on a big DO node

[02:36:50] <altendky> techalchemy: i'll have to read up on that, thanks.

[02:37:07] <techalchemy> they dont have a public view mode yet but it's my understanding that they will shortly

[02:38:07] <techalchemy> you can enable travis and use the old travis build on your fork if you want to see the actual status

[06:25:28] <thea> ^ would love any and all eyes on that PR.

[07:27:37] <pradyunsg> thea: I'll take a look. :)

[07:27:53] <pradyunsg> thea: if you don

[07:28:06] <pradyunsg> *don't mind, may I pm?

[07:36:55] <thea> Always, although I'm heading to bed and likely won't read until tomorrow.

[07:50:59] <pradyunsg> !logs

[07:50:59] <pmxbot> http://kafka.dcpython.org/channel/pypa-dev

[07:56:11] <pradyunsg> For the logs: https://git.io/vpbig is the PR thea mentioned.

[14:59:05] <cooperlees> I'll be annoying and ask again - any pip devs around to talk about adding --json to `pip download`

[14:59:07] <cooperlees> https://github.com/pypa/pip/pull/5400

[14:59:09] <cooperlees> :)

[15:09:41] <dstufft> cooperlees: I'll try to take a look later today

[15:09:54] <cooperlees> cheers

[15:48:01] <tomfbiz> dstufft -- I am at pycon sprinting for about 3 more hours. Any thoughts on something small I might work on? Could be researching a ticket that someone else could complete.

[15:59:29] <cooperlees> tomfbiz: Come to room 20

[16:18:52] <tomfbiz> cooperlees -- I am in room 20, at the table with you :-)

[16:19:27] <cooperlees> LoL

[17:14:01] <tomfbiz> dstufft -- I fixed test errors and lint errors. There is still one travis failure, but from what I can tell, that is not related to my PR. Can you confirm?

[17:14:19] <tomfbiz> https://github.com/pypa/pip/pull/5419

[17:16:38] <dstufft> tomfbiz: looks like wheel dropped support for 3.3

[17:24:16] <sigmavirus24> dstufft: more accurately they added the markers in setup.py to indicate the versions they actually support

[17:24:22] <sigmavirus24> I suppose they previously accidentally supported 3.3

[17:24:33] <dstufft> or that

[17:24:35] <dstufft> either way

[17:24:35] <sigmavirus24> And yes, that bit PyCQA in the rear too

[17:24:39] <dstufft> gonna kill 3.3

[17:24:42] <sigmavirus24> :fire:

[17:24:44] <dstufft> it was deprecated already

[17:36:15] <tomfbiz> dstufft -- ok if I make a PR to remove 3.3 from travis?

[17:36:33] <dstufft> tomfbiz: https://github.com/pypa/pip/pull/5423 :)

[17:36:37] <cooperlees> LoL

[17:36:41] <cooperlees> Timing

[17:38:22] <cooperlees> I was just saying to tomfbiz 1 mins before your PR came up he should just do the diff to remove 3.3 support

[17:38:47] <cooperlees> I'd love to see anonymous stats from Warehouse's perspective the use of CPython and PIP versions. Would love to work on that :)

[17:38:54] <cooperlees> + bandersnatch :P

[17:39:25] <dstufft> cooperlees: are you aware of the bigquery stats?

[17:39:53] <cooperlees> Yeah, but that does not show HTTP access to PyPI doe sit?

[17:39:55] <cooperlees> *does it

[17:40:32] <dstufft> cooperlees: each entry in the downloads table is a HTTP GET of a file from PyPI

[17:40:45] <cooperlees> O cool

[17:46:45] <tomfbiz> dstufft: I grabbed the .travis.yml part of your PR for removing python 3.3 so that my PR pass all CI passes before I leave Cleveland

[17:46:55] <dstufft> tomfbiz: sounds good

[18:03:01] <di_codes> asmacdo: <https://github.com/pypa/warehouse/pull/1006>

[18:43:27] <cooperlees> EWDurbin: You around at sprints still?

[18:43:37] <cooperlees> Just want to talk about getting a test API up to let people have a play etc.

[18:44:19] <cooperlees> Thinking possibly a separate container where we only run the new api on, and somehow only turn it on within that instance and people can get readonly access and use my client to see what the data looks like

[18:44:22] <cooperlees> dstufft: ^^

[18:44:41] <cooperlees> e.g. api-alpha.pypi.org

[18:46:41] <EWDurbin> cooperlees: I’m here but spent

[18:46:49] <EWDurbin> Absolutely spent

[18:49:47] <techalchemy> EWDurbin: psh organizing conferences is easy

[18:50:55] <cooperlees> EWDurbin: Totally understand

[18:57:08] <dstufft> cooperlees: We probably don't want to start deploying anything to pypi.org until we have more agreement on the exact shape of the API, I know that techalchemy wants to be part of that, and thea has expressed concerned about hypermedia vs an RPC based API and I need to spend some time with what y'all have worked on now that I'm home and can really dig into it :)

[18:58:21] <techalchemy> I don't have a formal allocation for how much time I can spend on open source but i'm pretty sure i've exceeded it this week :p

[18:58:33] <dstufft> heh

[18:58:42] <dstufft> yea, and folks probably need some time to recouperate from PyCon :)

[19:04:16] <cooperlees> Yeah, I would love to just get a initial poc up to allow people to see it and comment ... and allow easy iteration and leave it at alpha.pypi.org until ready

[19:05:43] <cooperlees> Ernest just showed us routes and how he’d want it. We’re gonna copy the forklift / upload setup and then Ernest said he can separate / protect it