Maybe a different way to say it is that the current TUF integration doc assumes that it is desirable to make minimal change to PyPI's layout and pip, easy_install, etc. while adding security. We made several choices based upon this assumption, including using and retaining the /simple dir.
If the community wants a more 'clean-slate' design, we could put that together also. This requires a lot of information specific to your setup and use cases so we'd appreciate collaboration with you guys to write that up. Thanks, Justin On Thu, Mar 14, 2013 at 8:14 AM, Trishank Karthik Kuppusamy < t...@students.poly.edu> wrote: > On 3/14/13 4:58 AM, holger krekel wrote: > >> >> I haven't followed the latest TUF discussions and related docs in >> depths yet but if those developments will regard "simple/" as a deprecated >> interface, i think this PEP here should maybe not introduce >> "simple/-with-externals" as it will just make the situation more >> complicated for everyone to understand in a few months from now. >> > > I haven't yet followed your PEP in as much depth as I would like, but I > wish to assure you that we do not regard "/simple/" as a deprecated > interface. In fact, we aim to preserve backwards-compatibility as much as > possible! :) > > > ______________________________**_________________ > Catalog-SIG mailing list > Catalog-SIG@python.org > http://mail.python.org/**mailman/listinfo/catalog-sig<http://mail.python.org/mailman/listinfo/catalog-sig> >
_______________________________________________ Catalog-SIG mailing list Catalog-SIG@python.org http://mail.python.org/mailman/listinfo/catalog-sig
