Added more examples that show that the u in the .1u format is a modifier to "1", not a format in itself.
Made the status of the "u" format modifier even more explicit.
More usual phrasing.
Even more explicit description of the u precision modifier.
More explicit phrasing.
More positive phrasing.
Simpler phrasing.
More explicit phrasing.
Additional, clearer example.
Merge branch 'release'
Merge branch 'master' into master_python2.3
Updated slightly obsolete documentation.
Reverted documentation to previous state: it was correct. Put more useful point first.
More precise documantation.
More explicit documentation (the formatting behavior for format specifications like 'u', '', 'g', etc. was not directly obvious: it is now emphasized.
Logic of the formatting doc now simpler.

Instead of focusing on the "uncertainty control mode", the doc now
focuses on precision given/not given. This is better because the
uncertainty control mode is activated by "u", but one may wonder what
happens with '' or 'f' since there is no "u" in the format
specification. Concretely, users must simply remember that the
precision (given or not) is key to defining the formatting behavior
(explicit precision vs automatic precision). It is very reasonable
that .2f keeps the same meaning as before, so users who want a
precision defined as a number of digits can remember to use .2uf
instead. When they want something automatic, they just don't mention
any precision (no need to confuse users with the "u" modifier, here).
Formatting doc on precision control now focuses more on the precision part than on the "uncertainty control mode" ("u" modifier).
More complete formatting documentation (defines the behavior of .2f).
Better consistency.
Recommended number form.