[Lxml-checkins] r51494 - in lxml/trunk: . doc

[scoder at codespeak.net]

Author: scoder
Date: Thu Feb 14 21:11:55 2008
New Revision: 51494

Modified:
   lxml/trunk/   (props changed)
   lxml/trunk/doc/objectify.txt
Log:
 r3509 at delle:  sbehnel | 2008-02-14 21:02:45 +0100
 doc cleanup


Modified: lxml/trunk/doc/objectify.txt
==============================================================================
--- lxml/trunk/doc/objectify.txt	(original)
+++ lxml/trunk/doc/objectify.txt	Thu Feb 14 21:11:55 2008
@@ -16,31 +16,6 @@
 used.  Python data types are extracted from XML content automatically and made
 available to the normal Python operators.
 
-To set up and use ``objectify``, you need both the ``lxml.etree`` module and
-``lxml.objectify``::
-
-    >>> from lxml import etree
-    >>> from lxml import objectify
-
-The objectify API is very different from the ElementTree API.  If it
-is used, it should not be mixed with other element implementations
-(such as trees parsed with ``lxml.etree``), to avoid non-obvious
-behaviour.
-
-The `benchmark page`_ has some hints on performance optimisation of code using
-lxml.objectify.
-
-To make the doctests in this document look a little nicer, we also use this:
-
-    >>> import lxml.usedoctest
-
-Imported from within a doctest, this relieves us from caring about the exact
-formatting of XML output.
-
-.. _Amara: http://uche.ogbuji.net/tech/4suite/amara/
-.. _gnosis.xml.objectify: http://gnosis.cx/download/
-.. _`benchmark page`: performance.html#lxml-objectify
-
 .. contents::
 ..
    1  The lxml.objectify API
@@ -61,6 +36,33 @@
      5.5  Advanced element class lookup
    6  What is different from lxml.etree?
 
+.. _Amara: http://uche.ogbuji.net/tech/4suite/amara/
+.. _gnosis.xml.objectify: http://gnosis.cx/download/
+.. _`benchmark page`: performance.html#lxml-objectify
+
+
+To set up and use ``objectify``, you need both the ``lxml.etree``
+module and ``lxml.objectify``::
+
+    >>> from lxml import etree
+    >>> from lxml import objectify
+
+The objectify API is very different from the ElementTree API.  If it
+is used, it should not be mixed with other element implementations
+(such as trees parsed with ``lxml.etree``), to avoid non-obvious
+behaviour.
+
+The `benchmark page`_ has some hints on performance optimisation of
+code using lxml.objectify.
+
+To make the doctests in this document look a little nicer, we also use
+this::
+
+    >>> import lxml.usedoctest
+
+Imported from within a doctest, this relieves us from caring about the exact
+formatting of XML output.
+
 
 The lxml.objectify API
 ======================