> 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 something I’d love to introduc
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:
On Tue, Dec 19, 2017, at
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 Py
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 m
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`
https://github.com/pypa/python-packaging-user-guide/is
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
>> ugly project pages that failed
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
__
> 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 lot of them on PyPI.
I fo
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
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
Hi,
Just following up on this proposal. I really do think it would be
beneficial to have limits on package deletion.
Thanks,
Jimmy Jia
On Wed, Nov 29, 2017 at 10:50 PM Jimmy Jia wrote:
> Hi everyone,
>
> This is moved over from
> https://github.com/pypa/packaging-problems/issues/112.
>
> Curre
11 matches
Mail list logo
