Hi Armin -- Can you speak a little more about how you'd see the workflow working with this new library? It seems a bit complex to have a library that's *copied* between Django and Jinja: I'd worry about patches getting lost.
For context, this has happened a few times with the simplejson and elementtree libraries in core Python: patches made to the upstream got "lost" before merging into Python's stdlib, and patches made against the stdlib didn't make it upstream. For a while there the json library in the stdlib was ever so slightly different from the simplejson library of supposedly the same version. Do you have ideas about how we could avoid this problem? (For the record, I wouldn't be opposed to having your proposed library be an external dependency. At some point the Python packaging ecosystem will be good enough that we can stop bundling, and I think we're getting pretty close to that point. But understood if that's a battle you don't want to fight :) Jacob -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
