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

Ben Finney bignose+hates-spam at benfinney.id.au
Wed Aug 1 05:33:54 CEST 2007


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.

"kirby.urner at gmail.com" <kirby.urner at gmail.com> writes:

> 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.
> 
> [... 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
wrapped at one length, and then each line broken again into a long and
a short line.

These are so awkward to read that I usually skip straight past them
without attempting to parse them, which isn't a benefit to anybody
(leaving aside snide remarks about the potential of negative value
from my contributions).

Is it some setting that users are enabling, or is it the default
behaviour?

More importantly, whom do we beat with the clue-by-four to make it
stop?

-- 
 \         "For of those to whom much is given, much is required."  -- |
  `\                                                   John F. Kennedy |
_o__)                                                                  |
Ben Finney



More information about the Python-list mailing list