Log file Viewer

[02:01:35] <techalchemy> thea: thanks for making that post

[04:24:22] <thea> No problem.

[11:40:31] <sumanah> pradyunsg: hey, I could REALLY use help creating more Good First Issues in pip and Warehouse

[11:40:52] <pradyunsg> sumanah: Sure thing! Happy to help.

[11:41:17] <sumanah> pradyunsg: the "please mark good first issues in your projects" email I sent to distutils-sig might help

[11:41:26] <sumanah> teensy tiny doc fix tasks,

[11:41:26] <sumanah> "manually test this functionality" tasks, and "check whether this bug is

[11:41:26] <sumanah> still reproducible" tasks

[11:41:31] <sumanah> all of them count

[11:42:42] <sumanah> And pradyunsg, after that, if you could do any review on https://github.com/pypa/warehouse/pulls that would be great

[11:43:19] <pradyunsg> sumanah: pip has 19 "good first issues" right now. If that's not enough, I am pretty sure I can add a few more "check if reproducible" ones.

[11:43:35] <sumanah> also pradyunsg this is a separate conversation but we were wondering yesterday (in a meeting of packaging and distribution folks): remind us of your current status regarding employment? you're a student, right? do you have a summer job lined up? if so, what months are you available? what year will you finish school?

[11:43:46] <sumanah> !logs

[11:43:46] <pmxbot> http://kafka.dcpython.org/channel/pypa-dev

[11:44:18] <sumanah> pradyunsg: I can point people to good first pip issues, thanks. I shall take 10 min now to try to add 1 or 2 more good first Warehouse issues and then try to add more in a few hours after my breakfast meeting

[11:46:02] <pradyunsg> sumanah: Still a student. No summer job lined up -- mostly going to learning things this summer and finishing unfinished work (pip's resolver). I have a summer break till July second week. 2020.

[11:46:33] <sumanah> pradyunsg: when does the summer break start?

[11:46:44] <sumanah> pradyunsg: anything in particular you are looking to learn?

[11:46:49] <pradyunsg> sumanah: it's ongoing. :)

[11:46:55] <sumanah> oh it already started? got it

[11:48:16] <sumanah> pradyunsg: are you potentially open to paid gigs between now and mid-July (particularly working on pip and related stuff)?

[11:48:38] <pradyunsg> sumanah: yep. Very much.

[11:49:11] <sumanah> pradyunsg: and what are any blockers or obstacles stopping you from working more effectively on pip during this time? hardware (laptop, CI), network connectivity, reviews from other folks, testing, bug triage.....?

[11:51:33] <pradyunsg> sumanah: I'm at home so networking and hardware are all good.

[11:51:54] <pradyunsg> sumanah: pip's CI (and tests in general) are something I'm definitely looking to improve. Same goes for the bug triage of the issue tracker.

[11:52:15] <sumanah> pradyunsg: on the CI side, is there any way paid services (or donated) could help?

[11:52:27] <sumanah> I hear the automated tests for pip currently take 40 min to run. Is that right?

[11:52:47] <pradyunsg> sumanah: Yep. It is correct.

[11:54:21] <pradyunsg> sumanah: One way the CI could improve in speed is more parallelization (since each test spawns multiple subprocesses).

[11:55:27] <pradyunsg> sumanah: The other is to actually making it more easier to write more unit tests. Slowly refactoring things and all that.

[11:55:41] <sumanah> ok

[11:55:55] <sumanah> pradyunsg: if you can think about any other ways money would help, that would be great

[11:56:00] <sumanah> we're trying to figure out what to ask companies for

[11:56:41] <pradyunsg> sumanah: Sure. I'll give it some thought and get back to you. :)

[11:56:52] <sumanah> Thanks

[11:57:12] <sumanah> pradyunsg: I know it's like 5:30pm where you are right now. About how long will you be on IRC? I may want some folks at this sprint to chat with you

[11:59:14] <pradyunsg> sumanah: I usually stay up till ~midnight.

[12:04:44] <sumanah> ok, thanks pradyunsg

[12:04:47] <sumanah> see you online later

[13:38:40] <cooperlees> dstufft: We're all gonna hang in IRC today if you're back

[14:38:32] <asmacdo> dstufft: we are wondering if you would prefer to keep the requirements minimal or if you would be open to adding a library for serialization

[14:38:59] <cooperlees> As in adding to the requirements of warehouse

[14:39:12] <cooperlees> cc: di_codes EWDurbin ^^

[14:45:05] <asmacdo> di_codes, dstufft, specifically, i'm looking at https://marshmallow.readthedocs.io/en/latest/ and https://github.com/marshmallow-code/apispec

[14:48:51] <fdrake> I'm playing with pipenv for the first time this week; my environment and workflow may not be what the pipenv developers expect in many ways. I'm trying to tell pipenv to create the virtualenv under the current directory using "PIPENV_VENV_IN_PROJECT=true pipenv install", but I'm getting the warning (which is really an error) "Warning: it looks like virtualenv is not in your PATH. We cannot continue until this is resolved."

[14:49:36] <fdrake> Building without setting PIPENV_VENV_IN_PROJECT works just fine.

[14:51:02] <fdrake> If I'm missing some docs on getting the environment set up, I'd appreciate a pointer.

[14:51:55] <cooperlees> di_codes: I see you've squatted https://pypi.org/project/pypi-api/ - What was you plan with this?

[14:52:31] <cooperlees> We were thinking of naming the client api and I was just checking what's available name wise on pypi

[15:11:07] <asmacdo> fdrake: you might want to check out #pipenv

[15:14:35] <di_codes> cooperlees: wasn’t it you that was talking about writing an importable api client for pypi?

[15:14:46] <cooperlees> Yup

[15:15:03] <cooperlees> basically wrapping aiohttp

[15:15:13] <cooperlees> s/wrapping/extending/

[15:24:24] <fdrake> asmacdo: Thanks! Didn't realize they had their own channel.

[15:40:31] <jaraco> https://docs.python.org/2/distutils/setupscript.html#listing-whole-packages

[16:35:00] <steiza_> @steiza -- Here is a linnk to the doc I've written https://etherpad.wikimedia.org/p/PyPA_Warehouse_2FA_notes

[17:23:13] <honzakral> waseem18: Hi, thanks for taking the time to look at #3111, I am here if you have any questions...

[17:24:19] <waseem18> honzakral: Hi - Your welcome and Thanks for taking time to review my PR.

[17:24:47] <waseem18> I've started looking into the review and will ping in here if I've any questions :)

[17:51:29] <dstufft> cooperlees: just got back to my computer, but I'm running back out to run to the store too :)

[17:51:57] <cooperlees> dstufft: No probs sir - expected commute time :)

[17:52:04] <cooperlees> I'll be hacking all night so I'll be around

[17:52:13] <dstufft> asmacdo: while still being frazzled and tired and trying to wind down from traveling, generically I give zero shits about adding more deps to warehouse. we have a ton of them and adding more is easy.

[17:52:26] <cooperlees> dstufft++

[17:52:40] <cooperlees> Have a relax today sir! You were under the pump here :)

[17:53:27] <di_codes> honzakral: is the version of ES that we’d migrate to 6.2.4?

[17:53:36] <honzakral> di_codes: yes, ideally

[18:32:39] <demophoon> Quick question regarding testing. I've got a python 3.3.5 test failure on my github PR regarding pip installing certifi that i'm not sure is related to any of my code changes.

[18:34:18] <demophoon> is there anyway to rerun those tests to see if it is my fault? I don't know if other people are running into these problems

[18:36:00] <di_codes> demophoon: providing a link to the build failure would be helpful

[18:36:28] <demophoon> oh right, sorry D:

[18:36:39] <demophoon> https://ci.appveyor.com/project/pypa/pip/build/1.0.2574/job/k2301m96o307ksof

[18:37:38] <thea> you can close and re-open the PR to re-trigger *all* CI builds, but it might be easier to get one of the admins to restart the appveyor build

[18:40:52] <demophoon> I'm not sure who those admins are :X i might just try amending the previous commit to see if that rekicks the job

[18:44:34] <thea> That'll definitely re-start the jobs

[18:45:22] <demophoon> Yup, they are going now. I'll just have to wait to see how that goes. Thanks

[19:46:25] <techalchemy> so did anything else come out of that discussion yesterday? Sorry I had to duck out, had a flight to catch

[19:46:30] <techalchemy> wish I would have stayed the extra day to stick around

[19:47:45] <thea> techalchemy: which discussion?

[19:48:14] <techalchemy> pypa summit talks

[19:48:31] <techalchemy> we skipped introductions, i realize, so that would be difficult to know that I was there or contributing i guess

[19:48:49] <thea> no worries. I just wanted context. :)

[19:49:03] <thea> I'm not sure but maybe some folks that are still at the sprints can chime in.

[20:29:35] <tomfbiz> I'm at the pycon sprint working on a ticket for pip.conf and I'm getting a strange error

[20:29:42] <tomfbiz> The directory '~/temp/pip-cache' or its parent directory is not owned by the current user and caching wheels has been disabled. check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.

[20:30:24] <tomfbiz> I just created directory ~/temp/pip-cache/

[20:30:55] <tomfbiz> I'm running a virtual environment -- would that cause this issue?

[20:40:22] <di_codes> honzakral: looks like the elasticsearch-dsl client for 6.x is setting the `_type` field to “doc” instead of the… class name maybe? i’m not sure how that was set in the past

[20:40:53] <di_codes> you can see it in this CI failure: <https://travis-ci.org/pypa/warehouse/jobs/379372340>

[20:45:20] <di_codes> i see this was a breaking change in 6.x but I’m not really sure how to migrate

[20:47:11] <tomfbiz> Nevermind -- apparently ~ is not expaNDED.

[21:07:09] <di_codes> (looks like it doesn’t really matter)