Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

404 for registered package with no release #1388

Open
inglesp opened this issue Jul 11, 2016 · 6 comments
Open

404 for registered package with no release #1388

inglesp opened this issue Jul 11, 2016 · 6 comments
Labels
needs discussion a product management/policy issue maintainers and users should discuss usability UX/UI design, user experience, user interface

Comments

@inglesp
Copy link

inglesp commented Jul 11, 2016

This was originally raised against PyPI.

When a package has been registered, but no release has been uploaded, Warehouse returns a 404. It would be more helpful if it displayed information about package.

For an example of this, see https://pypi.io/project/spider/.

@nlhkabu nlhkabu added the requires triaging maintainers need to do initial inspection of issue label Jul 12, 2016
@dstufft dstufft added Post launch - low priority and removed requires triaging maintainers need to do initial inspection of issue labels Jul 26, 2016
@reversefold
Copy link

How does one find out information about a registered package which has no releases? I tried to upload a package for which I thought the name was unused but got an error (see the linked ticket). I'd like to be able to contact the person who registered it as well as seeing how old the registration is but am not sure how to do so.

@FRidh FRidh mentioned this issue Jun 5, 2017
@brainwane brainwane added this to the 2: Shut Down Legacy PyPI milestone Nov 30, 2017
@brainwane brainwane added UX/UI design, user experience, user interface usability bug 🐛 needs discussion a product management/policy issue maintainers and users should discuss and removed Post launch - low priority labels Feb 26, 2018
@brainwane brainwane modified the milestones: 4: Launch: redirect pypi.python.org to pypi.org, 6. Post Legacy Shutdown Mar 12, 2018
@brainwane
Copy link
Contributor

Thanks for the bug report! And I'm sorry for the slow response.

In a Warehouse core developers' meeting earlier this month, we decided to pare down our near-future milestones on our development roadmap so they really only contain the essential bugfixes and features we need to launch, replace legacy PyPI, and shut down the old site. I see this behavior is currently the same on legacy PyPI and on the new site. So I'm moving this issue into a milestone further in the future; sorry for the wait.

I also think this may be related to the policy questions addressed in PEP 541 so I'm marking it with that tag as well, so that when that gets accepted, there'll be a little more clarity on how to properly address this.

Thank you again.

@di
Copy link
Member

di commented Mar 12, 2018

I'm not sure I would call this a "bug", but it's definitely un-ergonomic and can cause confusion when a new package author thinks a name has not been taken.

I think we either need to create a new page for this, or make the current project detail view handle a project with zero releases, either of which should indicate that the name is registered but has no releases (and possibly link to our PEP 541 policy/procedure).

@pradyunsg
Copy link
Contributor

Does this still need more discussion?

@di
Copy link
Member

di commented Jan 22, 2019

Yes, I think so. There are challenges to both:

  • Create a new page for this: what does this look like? How does it communicate to the user the state of this project? Do we really need a new page?
  • Make the current project detail view handle a project with zero releases: The "project" page is actually rendering a release, so without a release to render, it doesn't really work as intended.

@pradyunsg
Copy link
Contributor

pradyunsg commented Apr 8, 2022

I was looking at the code and, separately from the discussion above, the relevant page we'd add for this would need to be rendered at this point in the code:

https://github.com/pypa/warehouse/blob/96da89d80d7e8b4e025efbdb4ab485f697505f67/warehouse/packaging/views.py#L52

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs discussion a product management/policy issue maintainers and users should discuss usability UX/UI design, user experience, user interface
Projects
None yet
Development

No branches or pull requests

7 participants