It seems everyone that has chimed in prefers adding a dependency to vendoring. If there are alternative views please express them, but I'm going to recommend a dependency on the PR.
Thanks On Tuesday, 3 January 2017 09:13:01 UTC+11, Josh Smeaton wrote: > > I agree with Tim. I think the intent is to add dependencies as part of a > feature, not specifically as part of another DEP (which I don't believe > this feature needs). I don't think `overloading` was considered as a > dependency, but it's interesting. If this feature doesn't make 1.11 (it > potentially could if it's cleaned up) then perhaps we could take a better > look at overloading for 2.0. >> >> -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/394c70bf-b0fa-48d1-8cf2-6c0a690835bc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
