[20:34:25] <codepython7771> buck11: are you around?
[21:43:06] <buck11> scraper: i believe the plan is to release 1.6 soon-ish
[22:15:13] <IanLee1521> Hi all, so I've wanted to get more involved with contributing to things, started my first contribution in July to a Python library I was making use of and had a good experience of it. Now I was looking at pip as something that I had something I thought about contributing, and I was curious what the protocol for doing so was? Should I just do the work as a fork on GitHub and then pull request it? "Propose" it as a potential con
[22:32:37] <buck1> IanLee1521: write a ticket or better yet a pull request
[22:32:43] <buck1> and we'll discuss the merits there
[22:33:39] <buck1> if you want to avoid wasted time, might pitch the idea here
[22:34:50] <buck1> IanLee1521: this seems to be the standard etiquette for most any opensource project
[22:35:31] <IanLee1521> Yeah, I did the "make a pull request" as my previous experience.
[22:37:32] <IanLee1521> buck1: Seems like the way to go. I'll get something together soon. Thanks for the confirmation.
[22:37:46] <buck1> IanLee1521: what was it in particular?
[22:40:30] <IanLee1521> buck1: I was thinking of adding the '--user' option to the 'pip list' command as a way to return a list of just the packages that are installed to the user scheme. I've bumped into this a fair bit recently trying to figure out what packages are system wide vs in the user scheme. '--local' seems to handle this for virtual environments just fine already.