My personal feeling is most things that can be done out of core should be done out of core, but if new hooks or functionality is needed in core to accomplish that then we should consider adding it. The only exceptions are things that seem clear to affect a large percentage of the community or things that are implementing standards.
CORS is a great example of something that I *think* view derivers and a custom module should be able to do completely outside of core, but in the vein of CSRF are something that might benefit from being shipped with Pyramid if the implementation was deemed useful for a large percentage of use cases. - Michael On Thu, Sep 19, 2019 at 12:38 PM Theron Luhn <[email protected]> wrote: > Engaging with https://github.com/Pylons/pyramid/issues/3452 got me > thinking about functionality I’ve wished was shipped with Pyramid. CORS > for example, or a base traversal resource. > > So I was wondering what’s the bar to add additional stuff to the project? > Not an official policy or anything, just the general feeling of the > community. > > — Theron > > > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/pylons-discuss/AD1DB163-D691-4EF6-B8CA-A19F3D76E245%40luhn.com > <https://groups.google.com/d/msgid/pylons-discuss/AD1DB163-D691-4EF6-B8CA-A19F3D76E245%40luhn.com?utm_medium=email&utm_source=footer> > . > -- Michael -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/CAKdhhwExSZwM-kpVQUfYkFWDgeV%2B%3DZv%3DV%3DOFXMeLp-_T%2BrbOuA%40mail.gmail.com.
