Donald Stufft
Donald Stufft
I haven't read the entire PR yet, but you probably want this split over multiple deploys, currently what's going to happen is: 1. Column will be added, data migration will...
This is confusing, but the answer to how you do this today is that no matter what you need a `MANIFEST.in`. That is because the `MANIFEST.in` tells the toolchain what...
I think something like `twine configure` would be awesome.
FWIW, I don't want to say that I'm -1 on this specifically, but I don't think it's going to solve the use cases that people keep asking for like filtering...
The upload API does not support a warning mechanism, only error. Arguably it's better to send a warning via email though? Or at least one could make the argument that...
> Not really related to packaging itself but I wonder if PYPI could start archiving obsolete/unmaintained packages from the main index. PYPI UX could be improved if we would have...
> The main issue for the resolver is the metadata inaccuracies, which we really have no option other than to deal with directly in the resolver somehow. A new resolver...
Yes we do care. However it's largely a problem of there being bigger issues to tackle first. Sorry that nobody responded to your ticket though!
Yea its not really a big issue (and it's roughly equivalent to our current solution, which is hitting the update branch button). Which speaking of that, if I hit the...
I worry that the shuffle from Maintainer to Collaborator is a lot of churn for little value. The underlying problem with "just" adding the ability to yank to the `Maintainer`...