Re: Automation and other changes

2017-04-02 Thread Donald Stufft
> On Apr 2, 2017, at 1:26 PM, Donald Stufft <don...@stufft.io> wrote: > > Sounds like between my starting to lean towards it, your preference, and the > fact it would trigger a new mail notification for Paul’s workflow too, that a > special command is the way t

Re: Giving Pradyun Commit Access for Triaging

2017-06-26 Thread Donald Stufft
> On Jun 24, 2017, at 1:30 PM, Donald Stufft <don...@stufft.io> wrote: > > I’m going to give Pradyun commit access on the pip repository for the limited > purpose of triaging issues. This is done, I’ve created a new team called @pip-helpers which has write access

Re: NEWS entries for pip

2017-05-02 Thread Donald Stufft
> On May 2, 2017, at 4:08 PM, Paul Moore <p.f.mo...@gmail.com> wrote: > > On 2 May 2017 at 20:50, Donald Stufft <don...@stufft.io> wrote: >> It’s generally only a two step process if there isn’t an existing issue >> you’re fixing. If you’re fixing an issue yo

Remove access from inactive maintainers

2017-06-05 Thread Donald Stufft
so that they will be aware and can speak up themselves (BCC instead of CC so they don’t get spammed with any replies if they don’t care). Absent any objections, I’ll take these actions in the next couple of days (and I’ll need PyPI usernames for Paul and Xavier). — Donald Stufft

Re: Remove access from inactive maintainers

2017-06-06 Thread Donald Stufft
r managing that. So yea, totally fine with you being an owner. It doesn’t really affect the project itself much, being an owner mostly just gives you the rights/responsibility of managing teams/repos/etc when a new project gets added. — Donald Stufft

Re: New pip core developer: Pradyun Gedam

2017-10-06 Thread Donald Stufft
> On Oct 5, 2017, at 4:51 PM, Paul Moore wrote: > > Many of you will have seen the work Pradyun has been doing on the pip > tracker recently. He's been doing a fantastic job, and as a result, > we've offered him core developer status - and I'm pleased to say that > he's

Re: Disallow packages with the same name as stdlib modules

2017-10-25 Thread Donald Stufft
Sorry for the delay in response. So we actually *do* disallow package names with the same name as stdlib modules, however because there are a number of them that exist today and are useful (asyncio, ssl, etc) the way we’ve implemented this is that *new* projects cannot be created with the same

Re: [Distutils] Announcement: Pip 10 is coming, and will move all internal APIs

2017-10-22 Thread Donald Stufft
> On Oct 21, 2017, at 10:30 PM, Nick Coghlan wrote: > > However, none of that impacts the question of whether `pip.main()` runs code > in the current process or implicitly runs it in a subprocess - `pip` doesn't > import the modules it installs either way, so it will all

Re: PyPI JSON API redirect loop for all unpublished packages

2018-05-16 Thread Donald Stufft
> On May 16, 2018, at 5:06 PM, Doug Hellmann wrote: > > > > We had an issue testing redirect rules in the OpenStack documentation > build, so we built a tool to test the .htaccess files. I don't know > if whereto would be directly useful (maybe you're not using

Re: [Distutils] Announcement: Pip 10 is coming, and will move all internal APIs

2017-10-20 Thread Donald Stufft
> On Oct 20, 2017, at 9:30 AM, Paul Moore wrote: > > On 20 October 2017 at 14:26, Matthew Brett wrote: >> Thanks for the heads-up. >> >> Will y'all be doing a PyPI pre-release so we can test with `pip >> install --pre -U pip`? > > We've not yet

Re: statistics on downloads/request.logs

2018-03-15 Thread Donald Stufft
https://packaging.python.org/guides/analyzing-pypi-package-downloads/ > On Mar 15, 2018, at 7:16 PM, kenneth topp wrote: > > Hello, > > Are there any statistics of top downloaded pacakges/ api calls?

Re: Impending silent breakage of pip / macOS likely to cause severe confusion

2018-04-06 Thread Donald Stufft
> On Apr 6, 2018, at 4:28 PM, Matthew Brett wrote: > > > Ouch - it does look like we're in a very difficult situation, which > might apply to a significant number of users. > > I think the worst option is what we have ramping up in the brownout, > which is the silent

Re: Impending silent breakage of pip / macOS likely to cause severe confusion

2018-04-06 Thread Donald Stufft
> On Apr 6, 2018, at 12:30 PM, Matthew Brett <matthew.br...@gmail.com> wrote: > > Hi, > > On Fri, Apr 6, 2018 at 4:49 PM, Donald Stufft <don...@stufft.io > <mailto:don...@stufft.io>> wrote: >> >> On Apr 6, 2018, at 11:25 AM, Matthew Brett <m

Re: Impending silent breakage of pip / macOS likely to cause severe confusion

2018-04-09 Thread Donald Stufft
> On Apr 6, 2018, at 5:06 PM, Matthew Brett wrote: > > OK - so our hard deadline is the planned Warehouse launch on April > 16th? I would argue for going straight to the SSL error at that > point, and turning off the current brownout and April 8th TLS 1.0 shut > down.

Re: Impending silent breakage of pip / macOS likely to cause severe confusion

2018-04-06 Thread Donald Stufft
> On Apr 6, 2018, at 11:25 AM, Matthew Brett wrote: > > > As of 8th April, pip will break, largely in silence. As used with > default command line options, pip will stop seeing anything on pypi. > It will tell the user that it can't find packages that do exist on >

Re: [Distutils] Announcement: Pip 10 is coming, and will move all internal APIs

2018-04-14 Thread Donald Stufft
> On Apr 14, 2018, at 4:57 PM, Matthew Brett wrote: > > Is the suggestion to use the `_internal` import, or carry a copy of > the pep425tags code myself, that I have to keep up to date with the > internal pip copy? That would also involve me copying the `glibc` > part

Re: suggestion: using "black" for Warehouse formatting

2018-03-22 Thread Donald Stufft
So I considered that (and right now, it has a show stopper bug which means we can’t start using it), but given (A) pinning to a specific version (which means we’re not going to be open to _new_ bugs or changes in behavior and (B) we’re still running flake8 (at least in my branch) but I think