On Sun, Sep 28, 2014 at 10:28 PM, Marius Gedminas <[email protected]> wrote: > On Sun, Sep 28, 2014 at 02:21:11PM -0700, Chris Jerdonek wrote: >> Would this also affect the ability to update the "readme" information >> for a version on PyPI (i.e. the information displayed on the default >> home page generated by PyPI for the release) once the version has >> already been uploaded to PyPI? >> >> There are sometimes issues encountered with the display of that >> information that can't easily be checked without doing an actual >> version upload. > > restview has a --pypi-strict mode for this use-case #shamelessplug > https://pypi.python.org/pypi/restview > >> I haven't recently tried reuploading the metadata for a version, >> mainly because of uncertainty around how PyPI would handle it. > > In the past when I needed to fix stupid mistakes in my long_description, > I'd edit it using the web interface.
Thanks for the plug, Marius. But I should clarify that the metadata issues aren't restricted to the long_description. For example, there was a case where a co-maintainer of a project uploaded a new version of the project; and for reasons still unknown to me, the Trove classifiers did not render on the PyPI home page for the project, even though they rendered as expected for previous releases (and there was no change to the setup.py aside from the version). --Chris > > arius Gedminas > -- > if (DefRel.empty() == false) > -- apt-pkg/policy.cc (apt 0.5.23) > > _______________________________________________ > Distutils-SIG maillist - [email protected] > https://mail.python.org/mailman/listinfo/distutils-sig > _______________________________________________ Distutils-SIG maillist - [email protected] https://mail.python.org/mailman/listinfo/distutils-sig
