Author: Antonio Cuni <[email protected]> Branch: rpython-unicode-formatting Changeset: r56141:1ff292ef937e Date: 2012-07-18 14:51 +0200 http://bitbucket.org/pypy/pypy/changeset/1ff292ef937e/
Log: document string formatting diff --git a/pypy/doc/coding-guide.rst b/pypy/doc/coding-guide.rst --- a/pypy/doc/coding-guide.rst +++ b/pypy/doc/coding-guide.rst @@ -255,7 +255,12 @@ code if the translator can prove that they are non-negative. When slicing a string it is necessary to prove that the slice start and stop indexes are non-negative. There is no implicit str-to-unicode cast - anywhere. + anywhere. Simple string formatting using the ``%`` operator works, as long + as the format string is known at translation time; the only supported + formatting specifiers are ``%s``, ``%d``, ``%x``, ``%o``, ``%f``, plus + ``%r`` but only for user-defined instances. Modifiers such as conversion + flags, precision, length etc. are not supported. Moreover, it is forbidden + to mix unicode and strings when formatting. **tuples** _______________________________________________ pypy-commit mailing list [email protected] http://mail.python.org/mailman/listinfo/pypy-commit
