At 03:26 PM 2/5/2006 -0600, Ian Bicking wrote: >Even the most trivial of web applications needs templates to include >other templates, so the fact that this doesn't do anything to aid or >specify that makes the spec feel leaky. I can indicate where the >template comes from initially, but all bets are off after that.
As Ben has previously pointed out, systems like Myghty are going to ignore your 'find_template()' because they do their own finding. So the spec will leak no matter what, until we get to the level of specification called for by the "embedding" side of my proposal. (The compile/write stuff.) And Ben and Michael have both pointed out that trying to meet a spec that calls for them to change how their inner find_template works would be costly. Note, however, that these constraints don't have anything to do with whether WSGI is used or not; the essential complexity of the problem is still the same. _______________________________________________ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
