So, this proposition didn't really make sense to me. Folk like Linux distros will want the source, and you don't need to upload wheels :- setup.py could quite reasonably limit itself to software installation, vs configuration. Plenty of pip installable packages are not entirely ready to use after pip installation. -Rob On 17 Jan 2017 08:29, "Dariusz Suchojad" <dsuch@zato.io> wrote:
If you have a non-release release with some description text and a home-page that points to where active development is going on (that could constitute "functionality" in a non-code way), I think that should
On 16/01/17 22:19, Nick Timkovich wrote: preempt
a reasonable person (which is hopefully a superset of maintainers) from deleting it.
Yes, indeed, this is what I'd like to clarify. Someone is simply bound to clean up all the packages at one point and this PEP likely will be the basis for deciding what to delete or not so I'd very much like to ensure ours will not be removed.
regards,
-- Dariusz Suchojad
https://zato.io ESB, SOA, REST, APIs and Cloud Integrations in Python
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig