Am 20.07.2006 um 04:25 schrieb Todd O'Bryan:
>
> Is xml_escaped just too verbose? Seems very descriptive and
> unambiguous.
Do you mean
mark_xml_escaped for mark_safe,
XmlEscapedString for SafeString,
is_xml_escaped for is_safe (as function attribute)?
In the (long) discussion, this has alr
Is xml_escaped just too verbose? Seems very descriptive and unambiguous.
Todd
On Jul 19, 2006, at 4:56 PM, SmileyChris wrote:
>
>> 'escape' and 'safe' have a different meaning for fireworkers, too ;-)
> Or bank robbers :-P
>
> Back on topic, I like finalization too (even though I cringe having
Hi Chris,
Am 19.07.2006 um 22:56 schrieb SmileyChris:
> Back on topic, I like finalization too (even though I cringe having to
> write the american Z version).
Yeah, but default TZ is Chicago, so ... I chose zee. Be glad that
you're not forced to spell 'aluminum' somwhere!
The Old Britain Emp
> 'escape' and 'safe' have a different meaning for fireworkers, too ;-)
Or bank robbers :-P
Back on topic, I like finalization too (even though I cringe having to
write the american Z version).
--~--~-~--~~~---~--~~
You received this message because you are subsc
jeremy bornstein wrote:
> In some circles, "finalization" is what happens to an object immediately
> before it is GC'd, so this choice may end up being confusing. This is
> the case with respect to Java, for example.
Doesn't keep me from liking it, and Java is not python. Probably
each and eve
In some circles, "finalization" is what happens to an object immediately
before it is GC'd, so this choice may end up being confusing. This is
the case with respect to Java, for example.
On Tue, 18 Jul 2006 2:21 pm, Michael Radziej wrote:
>
> Hi,
>
> I made up my mind and I think I have the so
Hi,
I made up my mind and I think I have the solution (for the is_safe
terminology, django world domination, and all the rest :-)
* finalized *
So it's :
FinalizedString (replaced SafeString)
mark_finalized() (replaces mark_safe)
preserves_finalized (replaces is_safe as a function attrib
Malcolm Tredinnick wrote:
> If you want to mark every "still needs cooking" string then you have to
> mark *every* string that comes into the system (a la Perl's tainted
> strings).
Nonono ... I just was talking about terminology. We need a term
for "safe" and "unsafe" strings. I take it as gra
