Re: Google message munging (was: Live editing...)

On Jul 31, 10:38?pm, Paul Rubin wrote: > Ben Finney <[EMAIL PROTECTED]> writes: > > > [... more lines of broken line wrapping...] > > What the blazes is Google doing with messages that such a high > > proportion of them come through in this painful-to-read double-wrapped

Re: Google message munging (was: Live editing...)

> What the blazes is Google doing with messages that such a high > proportion of them come through in this painful-to-read double-wrapped > format? I'm referring to the fact that the lines appear to have been > wrapped at one length, and then each line broken again into a long and > a short line.

Re: [OT] Google message munging (was: Live editing...)

Ben Finney <[EMAIL PROTECTED]> writes: > > [... more lines of broken line wrapping...] > What the blazes is Google doing with messages that such a high > proportion of them come through in this painful-to-read double-wrapped > format? I'm referring to the fact that the lines appear to have been > w

[OT] Google message munging (was: Live editing...)

This is unrelated to the topic of the original poster, and is unrelated to Python; hence the off-topic marker. I'm also not saying anything targeted at the original poster, but rather using this message as an opportunity to ask a question. "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes: > There's

Live editing...

There's been some chatter on edu-sig (python.org) of late regarding Python's capabilities in the "edit/continue" tradition, meaning debugging tools, and/or IDE tools, that give the developer real time write access to running programs. I think a good design would be something like the ZODB, or the