search

pypi / warehouse

The Python Package Index
https://pypi.org
Apache License 2.0
3.58k stars 965 forks source link

How to update the "Description" in pypi.org ? #2170

Closed guolinke closed 6 years ago

guolinke commented 7 years ago

In the old pypi.python.org, we can update the description by using edit or upload a pkg-info file. But now it is not support:

Gone (This API has been deprecated and removed from legacy PyPI in favor of using the APIs available in the new PyPI.org implementation of PyPI (located at https://pypi.org/). For more information about migrating your use of this API to PyPI.org, please see https://packaging.python.org/guides/migrating-to-pypi-org/#uploading. For more information about the sunsetting of this API, please see https://mail.python.org/pipermail/distutils-sig/2017-June/030766.html)

But in pypi.org, I cannot find any function to add or change the description of the package : https://pypi.org/project/lightgbm/

I also tried to update it by using python setup.py register , but it failed: Server response (410): This API is no longer supported, instead simply upload the file.

So I tried to upload the pkg-file, but sill met the error: ValueError: Unknown distribution format: 'PKG-INFO'

ewdurbin commented 6 years ago

Howdy! I still feel shitty about how the entire Django metadata/python_requires situation went down. Dragging it up does more harm to my morale/person than it does to driving the conversation forward, @jobec.

Clearly this was a departure from the stated policy and a mistake.

I don't take actions on the index lightly. In the case of Django's botched python_requires setting, it was causing uninstallable versions of Django to be delivered to clients who were doing everything else right. Ultimately having the inaugural version of Django dropping Python 2 support involved caught the better of me in being eager to help.

Moving forward I'll expressly avoid such intervention. The policy for PyPI is immutable metadata.

This is no longer a feature discussion. Future comments on this discussion that fly snark in passing won't be tolerated. Please be mindful of the impact that words have on the folks who are eager to help the community.

jaraco commented 2 years ago

I'd like to add another use-case to the discussion above. Today, I'm making the first update to https://pypi.org/project/backports, a project with nothing but metadata. That is, it has no code and no downloads. I'd like to update the project without uploading any new artifacts or creating any new versions. It would be nice if there were a way to perform the equivalent operation, something like twine refresh-metadata dist/backports*.tar.gz (or twine register dist/*).

pradyunsg commented 2 years ago

@jaraco Please file a new issue to discuss this, rather than commenting on a closed and locked issue from almost three years ago.

pradyunsg commented 2 years ago

Unlocked and relocked to surface any x-refs made over the last three years.

https://github.com/pypa/warehouse/issues/4816 is probably where you want to comment.