Stefan Behnel wrote:
Nick Coghlan wrote
a) Patches are more likely to be looked at if placed on the SF patch
tracker.
see your own b), I wanted to discuss them first.
Fair enough.
Still, when I first tried out the Template class, I immediately stumbled
over the fact that the substitute methods
Nick Coghlan <[EMAIL PROTECTED]> wrote:
>
> a) Patches are more likely to be looked at if placed on the SF patch tracker.
>
> b) I don't quite see the point, given how easy these are to spell using the
> basic safe_substitute. You're replacing one liners with one-liners.
c) add a documentati
Nick Coghlan wrote
a) Patches are more likely to be looked at if placed on the SF patch
tracker.
see your own b), I wanted to discuss them first.
b) I don't quite see the point, given how easy these are to spell using
the basic safe_substitute. You're replacing one liners with one-liners.
Still,
a) Patches are more likely to be looked at if placed on the SF patch
tracker.
b) I don't quite see the point, given how easy these are to spell using the
basic safe_substitute. You're replacing one liners with one-liners.
Cheers,
Nick.
--
Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Aust
Hi!
Here's a trivial patch against Lib/string.py that adds two new methods. The
first replaces the template by a partially resolved substitution and the
second creates a new, partially substituted template. I find those two useful
enough for integration in the stdlib, especially the replacing on
