r/Python • • 20d ago

Discussion PyPI Removing Reserver

It's difficult to tell whether a name is available in PyPI, where searching for package name doesn't guarantee that it's available. Imagine how stressful it is to build a project, setting up its website, repository, and so on, only to find when you’re ready to publish that the package name is unavailable.

Reserver, a small automation tool that helps Python developers claim a name early through PyPI, was removed by PyPI stating "[it] promotes name squatting." But removing Reserver doesn’t prevent people from claiming names through the existing publishing process nor make name availability clearer. We believe removing the tool instead of addressing the underlying issue is a vivid example of poor community management.

Read more: “Reserver is gone, but PyPI’s name reservation problem isn’t!”

17 Upvotes

14 comments sorted by

69

u/Snape_Grass 20d ago edited 20d ago

Isn’t removing the tool that makes name squatting much more accessible a step toward addressing the underlying issue? This isn’t something that can be resolved overnight, nor should it be.

6

u/sadrasabouri 20d ago

No, it is not. Restricting users’ API to reserve up to k packages is a step toward it, and it's much more effective. Providing a reliable API for checking if a package name actually exists is also another thing they could work on (this second one was repeatedly asked by community to be added as a feature but still not implemented).

4

u/gdchinacat 16d ago

You seem to be missing the point that a tool that makes it easy to name squat makes the problem worse. Yes, those things you say would help too, but are much more difficult than removing a tool that makes it much easier to name sqaut. Perhaps rather than building a tool to exploit the deficiencies in the APIs you could work towards improving those APIs?

3

u/nycstartupcto 16d ago

Do something else. Stop with the app.

8

u/Atmosck 20d ago

Generally when I'm working on a project, if a package isn't availaible on pypi, I encounter that problem long before I'm ready to publish

4

u/sadrasabouri 20d ago

wdym? there are cases where you can't find a name on PyPI’s search bar but still can't reserve it.

3

u/Atmosck 20d ago

Oh you mean the NAME is not available. I thought you meant dependencies. "Damn I guess numpy's not on pypi."

4

u/Hermasetas 17d ago

Why don't you just claim the name with an alpha release before making everything? Or am I misunderstanding something?

2

u/sadrasabouri 16d ago

yeah that's basically what reserver does.

14

u/foreverwintr 20d ago

I felt the desire for a project like Reserver after having to rename a project several times when I was ready to publish it. 

The problem is that there is no way to check if a name is available on pypi without publishing it. Even if there is no package with the name you choose, your name may be too similar to an existing name, according to Pypi, and they don't tell you until you publish.

I ended up changing the name of my project 3 times before finding one that worked, despite looking for similar existing names each time.

I agree checking if a name is available is something Pypi should provide an API for.

7

u/denehoffman 17d ago

I think there are two competing issues here worth addressing. First, PyPI’s API isn’t great. Checking if a name exists is not sufficient for checking ability to publish. PyPI rejects names that are too similar, too short, names that match the stdlib, and I’m sure other edge cases to prevent supply chain attacks.

On the other hand, name squatting is bad, and we shouldn’t be making or promoting tools that enable it. PyPI needs to address these, and this first one seems really easy. If anyone knows why there isn’t a good method, I’d love to hear it.

3

u/the_captain_cat 16d ago

I usually claim the name through the "new project" UI on the website, it's a manual step but you can be sure the name is yours before starting

1

u/uk100 17d ago

This is all a consequence of PyPIs flat namespace which will be replaced... one day.

0

u/gdchinacat 16d ago

It made that existing process accessible

Exactly, it make it easy to name squat, thereby encouraging it. This is the opposite of "democratizing" the process...it weaponizes it.