Re: [Distutils] The mypy package

On Tue, Apr 19, 2016 at 7:59 AM, Nick Coghlan wrote: > However, as others have noted, we don't really have the resources to > administer a PyPI name dispute resolution system - when there are legal > issues, the PyPI admins can escalate matters to the PSF Board (but those >

Re: [Distutils] The mypy package

On 19 April 2016 at 01:21, Jim Fulton wrote: > I suggest measuring activity by downloads, not releases. Sometimes > maintained packages are boring enough not to need releases, while many > projects depend on them. > Standard library backport packages are fairly prone to

Re: [Distutils] The mypy package

I described at a high level what mypy-lang does to my wife, and the brief history of this issue. Her blerted out solution was to "just change mypy-lang to annopy" (for annotated python). I am required by marital obligation to bring that forward. On 4/18/2016 18:21, Glyph wrote: On Apr

Re: [Distutils] The mypy package

On Mon, Apr 18, 2016 at 11:47 PM, Chris Barker wrote: > > I'm suggesting that the "in perpetuity" bit is NOT a good way to go -- > packages are abandoned, and the longer this goes on, the more issues will > arise. > > ​Problem is cat's out of the bag here. There are three

Re: [Distutils] The mypy package

> On Apr 18, 2016, at 3:17 PM, Alex Grönholm wrote: > > This name is unfortunately a bit awkward in the author's native language -- > it is the colloquial word for "babe" or "broad" :) OK, I didn't see that one coming :-). "stapy", then? "static type annotation

Re: [Distutils] The mypy package

> On Apr 18, 2016, at 2:00 PM, Chris Barker wrote: > > On Mon, Apr 18, 2016 at 9:37 AM, Alexander Walters > wrote: > Greatly expanding the pool of names solves the problem. > > some of it, maybe, but not the

Re: [Distutils] The mypy package

On Mon, Apr 18, 2016 at 9:37 AM, Alexander Walters wrote: > Greatly expanding the pool of names solves the problem. > some of it, maybe, but not the problem at hand -- mypy has already put itself up as "mypy-lang", an namespace would be pretty much the same thing. if

Re: [Distutils] The mypy package

On Mon, Apr 18, 2016 at 9:41 AM, David Wilson wrote: > > huh? as far as I can tell, namespaces greatly expand the pool of > available > > names, but other than that, we've got the same problem. > > They seem to have worked well enough from the 1980s through to the

Re: [Distutils] The mypy package

On Mon, Apr 18, 2016 at 9:30 AM, Alexander Walters wrote: > We absolutely do not. Names are first come, first serve, in perpetuity. I'm suggesting that the "in perpetuity" bit is NOT a good way to go -- packages are abandoned, and the longer this goes on, the more

Re: [Distutils] The mypy package

On Mon, Apr 18, 2016 at 09:34:09AM -0700, Chris Barker wrote: > Namespaces seem like a great idea, then these problems disappear > entirely, > huh? as far as I can tell, namespaces greatly expand the pool of available > names, but other than that, we've got the same problem. They seem

Re: [Distutils] The mypy package

On Mon, Apr 18, 2016 at 08:18:37AM -0700, Chris Barker - NOAA Federal wrote: > We really should have SOME way to determine if a PyPi name has been > abandoned. Or even be proactive--PyPi names must be maintained in SOME > way, perhaps: +1 > Respond to some sort of "do you still want this"

Re: [Distutils] The mypy package

Greatly expanding the pool of names solves the problem. On 4/18/2016 12:34, Chris Barker wrote: On Mon, Apr 18, 2016 at 8:48 AM, David Wilson > wrote: Namespaces seem like a great idea, then these problems disappear

Re: [Distutils] The mypy package

On Mon, Apr 18, 2016 at 8:48 AM, David Wilson wrote: > Namespaces seem like a great idea, then these problems disappear > entirely, huh? as far as I can tell, namespaces greatly expand the pool of available names, but other than that, we've got the same problem.

Re: [Distutils] The mypy package

On Mon, Apr 18, 2016 at 8:21 AM, Jim Fulton wrote: > I suggest measuring activity by downloads, not releases. Sometimes > maintained packages are boring enough not to need releases, while many > projects depend on them. > so this is the tricky bit -- in the mypy case, it's

Re: [Distutils] The mypy package

On 4/18/2016 11:18, Chris Barker - NOAA Federal wrote: Domain names are a different system -- you need to maintain your registration. Except, that wasn't my point. My point was I ignore people asking to buy my domain from me because the registered name is part of my identity. PyPi names, on

Re: [Distutils] The mypy package

On Mon, Apr 18, 2016 at 10:21 AM, Jim Fulton wrote: > I suggest measuring activity by downloads, not releases. Sometimes > maintained packages are boring enough not to need releases, while many > projects depend on them. > I don't know about on pypi, but I know in general

Re: [Distutils] The mypy package

I suggest measuring activity by downloads, not releases. Sometimes maintained packages are boring enough not to need releases, while many projects depend on them. Jim On Mon, Apr 18, 2016 at 11:18 AM, Chris Barker - NOAA Federal wrote: >> Though I do wonder how effective

Re: [Distutils] The mypy package

> Though I do wonder how effective that would be in this case. For all we > know, in the case of mypy, the maintainer is simply ignoring someone else who > is trying to take the name they registered. (I get emails all the time for > people trying to get me to sign over my domain names;

Re: [Distutils] The mypy package

On 18 April 2016 at 08:46, Guido van Rossum wrote: > In a similar vein, the package distributor is listed as "zuroc" -- would > this be someone else or just an alias for the owner? > That's the same person mentioned in your original mail. Richard

Re: [Distutils] The mypy package

Hm, interesting idea. I probably know someone at work who can help me translate. In a similar vein, the package distributor is listed as "zuroc" -- would this be someone else or just an alias for the owner? On Sat, Apr 16, 2016 at 11:38 PM, Ionel Cristian Mărieș wrote: > >

Re: [Distutils] The mypy package

On Sat, Apr 16, 2016 at 2:29 AM, Guido van Rossum wrote: > Both Donald and myself have approached the owner (zsp...@gmail.com) but > not received any response. > ​Have you considered getting someone to write an email in Chinese?​ I suspect he did not understand what was asked

Re: [Distutils] The mypy package

On 4/16/2016 14:52, Paul Moore wrote: We >cant unilaterally hand over names on pypi to unrelated.. or even related.. >projects because they have a name someone else wants. What I*meant* to say here was that when a request for a name transfer gets no reply, it's helpful to know if the email

Re: [Distutils] The mypy package

Sorry, please ignore that email. I hit "Send" too soon. > We > cant unilaterally hand over names on pypi to unrelated.. or even related.. > projects because they have a name someone else wants. What I *meant* to say here was that when a request for a name transfer gets no reply, it's helpful to

Re: [Distutils] The mypy package

On 16 April 2016 at 17:42, Alexander Walters wrote: > To what end? To the end of ensuring that people can get in touch with project owners. > As much as old packages cluttering the namespace of pypi is > annoying, the only thing that will accomplish is orphaning

Re: [Distutils] The mypy package

> On Apr 16, 2016, at 12:42 PM, Alexander Walters > wrote: > > Another solution like adding namespaces to pypi sounds better to me... but > then I think about the nightmare of implementing that in a backwards > compatible way. We already have namespacing sort of,

Re: [Distutils] The mypy package

To what end? As much as old packages cluttering the namespace of pypi is annoying, the only thing that will accomplish is orphaning projects. We cant unilaterally hand over names on pypi to unrelated.. or even related.. projects because they have a name someone else wants. Another solution

Re: [Distutils] The mypy package

On 16 April 2016 at 01:10, Richard Jones wrote: > Because this sort of thing has come up a lot in the past, and because I've > copped trouble for mishandling it in the past, I took the trouble of writing > up a formal description of how I handle these sorts of issues: > >

Re: [Distutils] The mypy package

On Fri, Apr 15, 2016 at 8:59 PM, Guido van Rossum wrote: > Another thing. Is the search index on pypi.python.org no longer being > updated? Searching for mypy-lang still takes you to mypy-lang 0.2.0, even > though 0.3.1 has been released many weeks ago. I just updated the typing

Re: [Distutils] The mypy package

Another thing. Is the search index on pypi.python.org no longer being updated? Searching for mypy-lang still takes you to mypy-lang 0.2.0, even though 0.3.1 has been released many weeks ago. I just updated the typing package and searching for that still shows the old versions. On Fri, Apr 15,

Re: [Distutils] The mypy package

Oh well. I wonder if offering money would change the situation. On Fri, Apr 15, 2016 at 5:10 PM, Richard Jones wrote: > Hi Guido, > > Because this sort of thing has come up a lot in the past, and because I've > copped trouble for mishandling it in the past, I took the

Re: [Distutils] The mypy package

Why are you so determined to use the name "mypy" in the first place? Seems to me it's a terrible name. It sounds more like a working title for someone's personal implementation of Python, and certainly gives no clue that it has anything to do with type checking. So instead of trying to steal the

Re: [Distutils] The mypy package

Hi Guido, Because this sort of thing has come up a lot in the past, and because I've copped trouble for mishandling it in the past, I took the trouble of writing up a formal description of how I handle these sorts of issues:

Re: [Distutils] The mypy package

I've fallen into this trap as well, so +1 for the takeover. It might be a good idea to come up with a standardized process for taking over old, unmaintained packages. 16.04.2016, 02:29, Guido van Rossum kirjoitti: Brett suggested I ask the kind folks here. As you may or may not know,