PMXBOT Log file Viewer

Help | Karma | Search:

#pypa-dev logs for Thursday the 16th of April, 2020

(Back to #pypa-dev overview) (Back to channel listing) (Animate logs)
[14:48:08] <dstufft> We should probably have something that compacts that table over time into rollup tables
[18:00:05] <pradyunsg> Is there some 0kb usage way to do a COUNT(*) with the new tables structure? It's fine if that's no longer possible, but just wanted to check. https://gist.github.com/pradyunsg/8a78b7f743fdbcb198bdd8140b1b9a3a
[18:19:25] <sumanah> I'm trying to pull together a concise summary of the major projects/endeavors that are happening right now in packaging development -- Bernat is going strong on the virtualenv development, techalchemy is working on getting the new pipenv release out, and there's the stuff listed in https://pyfound.blogspot.com/2020/04/sponsoring-python-packaging.html
[18:20:55] <sumanah> (this is for a single slide in a 5-minute lightning talk during the Language Summit later today)
[18:21:14] <sumanah> jaraco: is there a substantial push of some kind re setuptools that I should know about/mention?
[18:26:30] <pradyunsg> We're working on an independent library `installer` for installing wheels.
[18:26:38] <techalchemy> yay
[18:26:44] <pradyunsg> https://github.com/pradyunsg/installer/issues/1
[18:26:51] <sumanah> pradyunsg: that's great! but also you need to go to sleep soon ;-)
[18:27:14] <pradyunsg> sumanah: yup yup.
[18:27:24] <pradyunsg> :)
[18:37:35] <techalchemy> pradyunsg, btw i think you asked me some time ago about something related to the code I had to crawl for wheels and introspect them
[19:07:23] <sumanah> techalchemy: lemme guess: you are in a meeting
[19:42:42] <sumanah> jaraco: ping re my question above ^ as I try to finalise my little talk
[19:44:52] <techalchemy> sumanah, not in a meeting atm
[19:44:59] <techalchemy> i see your question was awhile ago though
[19:44:59] <techalchemy> :p
[19:45:20] <sumanah> hee!
[19:45:34] <sumanah> so techalchemy, as I remember, you're trying to get the Pyup API key situation sorted out
[19:45:37] <sumanah> how's that going?
[19:45:40] <sumanah> if now is an ok time to ask
[19:45:57] <techalchemy> will know in 15 mins, talking to someone from pyup at 4
[19:46:59] <sumanah> great techalchemy - lemme know if you for any reason want me in that call too
[19:48:01] <techalchemy> sumanah, sure, I think it might be possible to just use pyup's api on a slight lag for free now without an api key since the last week or so, which might be fine
[19:52:39] <techalchemy> as in, their most current data is gated behind the key but otherwise access is unrestricted; alternatively their entire database is on github and is CC-BY-NC-SA which we could potentially access on the fly
[19:53:52] <sumanah> but how many hits/second would that be? I presume you're talking about hitting hte GitHub API techalchemy ?
[19:54:48] <techalchemy> sumanah, it'd be the raw.github.com/ endpoint to grab a json file, likely caching it at least for 6 hours at a time but probably could be 24hrs or more
[19:55:12] <techalchemy> i dont -think- it's a substantial amount of traffic
[19:56:09] <sumanah> that seems like something we could ask in 4 min techalchemy
[19:56:18] <sumanah> asking how much traffic we were sending them
[20:15:42] <techalchemy> thanks sumanah!
[20:15:47] <sumanah> techalchemy: glad to contribute
[20:16:04] <sumanah> techalchemy: ok. so, next steps? look at Safety? I didn't catch some of the details
[20:16:21] <techalchemy> yeah apparently the key is just unnecessary with the later releases
[20:16:35] <techalchemy> but might require changing where it looks for a database
[20:16:53] <sumanah> maybe you could write a quick summary of the call in the relevant pipenv GitHub issue, just to keep the users apprised, and then go implement stuff?
[20:16:57] <techalchemy> sure thing
[20:17:02] <sumanah> [thumb up]
[20:28:09] <jaraco> sumanah: Setuptools is dropping support for Python 2 (as soon as next week). importlib.resources and importlib.metadata (and their backports) are getting lots of love with ambitions of obviating 99% of `pkg_resources` usage. PEP517/518 support is maturing toward production-ready.
[20:28:49] <sumanah> Thank you jaraco!
[20:29:07] <jaraco> You bet; only wish I’d seen the message sooner.
[20:29:30] <sumanah> no prob on my end :-) it all worked out
[20:32:16] <sumanah> I'm trying to think of other things that I should sum up as "in progress"
[20:34:35] <techalchemy> sumanah, lol, based on the convo i tried setting PIPENV_PYUP_API_KEY=""
[20:34:42] <techalchemy> apparently that fixes the issue
[20:34:54] <techalchemy> like, as an environment variable...
[20:35:55] <sumanah> awesome?
[20:36:25] <travis-ci> pypa/pip#15757 (master - 6f7d5b9 : Pradyun Gedam): The build passed.
[20:36:25] <travis-ci> Change view : https://github.com/pypa/pip/compare/2f3a1be1185e...6f7d5b9ae945
[20:36:25] <travis-ci> Build details : https://travis-ci.org/pypa/pip/builds/675916237
[20:37:28] <techalchemy> yah
[21:05:22] <sumanah> techalchemy: ok, so, am I right that this will (we hope) not take more than a day to implement and test?
[22:36:47] <travis-ci> pypa/twine#1368 (master - f7402e0 : Brian Rutledge): The build passed.
[22:36:47] <travis-ci> Change view : https://github.com/pypa/twine/compare/5482d6877df0cd90545c4708e5abe13b359f8a08...f7402e0d2e1c1e6ecde61dc8bcba515b807a48a0
[22:36:47] <travis-ci> Build details : https://travis-ci.org/pypa/twine/builds/675975010
[22:49:01] <travis-ci> pypa/pip#15758 (master - 6f7d5b9 : Pradyun Gedam): The build passed.
[22:49:01] <travis-ci> Change view : https://github.com/pypa/pip/compare/2f3a1be1185e3434c0c8d9cc58d4271beff1d122...6f7d5b9ae94543d9096eeb330d7ee2497ec82d9b
[22:49:01] <travis-ci> Build details : https://travis-ci.org/pypa/pip/builds/675969301
[23:46:32] <travis-ci> pypa/twine#1369 (master - ebd99ae : Ian Stapleton Cordasco): The build passed.
[23:46:32] <travis-ci> Change view : https://github.com/pypa/twine/compare/f7402e0d2e1c...ebd99aed6334
[23:46:32] <travis-ci> Build details : https://travis-ci.org/pypa/twine/builds/675994350