Samuel Bishop

Ok... so 5 years have passed... is this still "temporary" half a decade later? or has this just become an accepted limitation that will never be resolved? Personal Note: This...

CLA signed.

I'd say the same statement applies for using any templating engine that supports partials/includes, such as swig.

Feature parity with this would be nice, http://waffle.readthedocs.org/en/latest/usage.html#waffle-in-javascript

https://github.com/wq/django-swappable-models might be a solution to this. If the goal is to make it swappable just like the Django user profile model is. But given how tough it can be...

I might have some ideas how to get these queries to come out more optimised, but I'm not 100% sure if I've followed your reasoning correctly. This definitely seems like...

@hugobessa Its just occurred to me that any work to improve this may have conflicts with the work to make the Tennant model swappable and solve #37

While a useful and valid tool, it is generally considered something to be avoided unless necessary. As someone that just started using this library I'd prefer to see thread locals...

I do agree it makes it more organised. However for the same reasons outlined in the rational section of [PEP 567](https://www.python.org/dev/peps/pep-0567/#rationale) I think thread local storage based solutions are less...

I while this is the WSDL 2 spec, there's no reason Soapfish can't grow to support for that so he tests are helpful. I went looking for equivalent tests for...