Re: [Distutils] Immutability of Release Metadata in Warehouse

On 20 December 2017 at 05:58, Donald Stufft wrote: > However! There is a desire to enable Markdown support for PyPI, and as part > of that a new metadata field is being added that just indicates what format > the description is in (rst, markdown, or plaintext is the supported

Re: [Distutils] Immutability of Release Metadata in Warehouse

Another thing that arises with yanking is the idea of deprecating releases or packages. While in many cases yanking is sufficient, it's nice to have a way to explicitly deprecate rather than yank packages that are e.g. no longer maintained, have been renamed, or have better replacements, without

Re: [Distutils] Immutability of Release Metadata in Warehouse

> On Dec 19, 2017, at 4:30 PM, Matthias Bussonnier > wrote: > > One alternative is have the ability to "yank" a package. Make it still > available, but installable only when pinned explicitly. I believe that's what > Rust does. The ability to yank a package is

Re: [Distutils] Immutability of Release Metadata in Warehouse

I support the goal of making metadata match files as well. One alternative is have the ability to "yank" a package. Make it still available, but installable only when pinned explicitly. I believe that's what Rust does. -- M On Dec 19, 2017 22:21, "Thomas Kluyver" wrote:

Re: [Distutils] Immutability of Release Metadata in Warehouse

On Tue, Dec 19, 2017, at 9:10 PM, Matthias Bussonnier wrote: > One case I could see is the use of the requires_python metadata. It > was not included in the recent release of Django 2.0 (which is py 3 > only) and making a new release will be useless as pip on py2 will > still see Django 2.0.0 as

Re: [Distutils] Immutability of Release Metadata in Warehouse

One case I could see is the use of the requires_python metadata. It was not included in the recent release of Django 2.0 (which is py 3 only) and making a new release will be useless as pip on py2 will still see Django 2.0.0 as Py 2 compatible download it and crash. I'm going to assume with time

Re: [Distutils] Immutability of Release Metadata in Warehouse

For those who want to track the relevant GitHub issues: * supporting Markdown https://github.com/pypa/warehouse/issues/869 * staged releases https://github.com/pypa/warehouse/issues/726 * advising packagers to run `python setup.py check -r -s`

Re: [Distutils] Immutability of Release Metadata in Warehouse

On 12/19/2017 02:58 PM, Donald Stufft wrote: > >> On Dec 19, 2017, at 2:51 PM, Alex Grönholm wrote: >> >> Couldn't Warehouse validate the description, and reject the upload (with an >> appropriate message) if it doesn't pass? This at least would eliminate those >>

Re: [Distutils] Immutability of Release Metadata in Warehouse

On 12/19/2017 03:00 PM, Sumana Harihareswara wrote: > * supporting Markdown https://github.com/pypa/warehouse/issues/2206 Whoops: https://github.com/pypa/warehouse/issues/869 is the right link. -- Sumana Harihareswara Changeset Consulting https://changeset.nyc

Re: [Distutils] Immutability of Release Metadata in Warehouse

> On Dec 19, 2017, at 2:51 PM, Alex Grönholm wrote: > > Couldn't Warehouse validate the description, and reject the upload (with an > appropriate message) if it doesn't pass? This at least would eliminate those > ugly project pages that failed to render...there are a

Re: [Distutils] Immutability of Release Metadata in Warehouse

Couldn't Warehouse validate the description, and reject the upload (with an appropriate message) if it doesn't pass? This at least would eliminate those ugly project pages that failed to render...there are a lot of them on PyPI. Donald Stufft kirjoitti 19.12.2017 klo 21:43: For those who are

[Distutils] Immutability of Release Metadata in Warehouse

For those who are not aware, legacy PyPI would allow you to run ``twine register`` on a release that had already been created in order to modify the metadata that PyPI had recorded for that release (keyed by version number). This wasn’t a super widely used feature, but it’s primary use case was