diff --git a/doc/FAQ.txt b/doc/FAQ.txt index f9da7b4ce..e7c35cfce 100644 --- a/doc/FAQ.txt +++ b/doc/FAQ.txt @@ -129,7 +129,7 @@ The `generated API documentation`_ is a comprehensive API reference for the lxml package. .. _`ElementTree API`: http://effbot.org/zone/element-index.htm -.. _`the web page`: http://codespeak.net/lxml/#documentation +.. _`the web page`: http://lxml.de/#documentation .. _`generated API documentation`: api/index.html @@ -472,8 +472,8 @@ implement but didn't due to lack if time. If *you* find the time, patches are very welcome. .. _ReST: http://docutils.sourceforge.net/rst.html -.. _`text files`: http://codespeak.net/svn/lxml/trunk/doc/ -.. _`list of missing features`: http://codespeak.net/svn/lxml/trunk/IDEAS.txt +.. _`text files`: https://github.com/lxml/lxml/tree/master/doc +.. _`list of missing features`: https://github.com/lxml/lxml/blob/master/IDEAS.txt Besides enhancing the code, there are a lot of places where you can help the project and its user base. You can @@ -555,7 +555,7 @@ First, you should look at the `current developer changelog`_ to see if this is a known problem that has already been fixed in the SVN trunk since the release you are using. -.. _`current developer changelog`: http://codespeak.net/svn/lxml/trunk/CHANGES.txt +.. _`current developer changelog`: https://github.com/lxml/lxml/blob/master/CHANGES.txt Also, the 'crash' section above has a few good advices what to try to see if the problem is really in lxml - and not in your setup. Believe it or not, @@ -598,7 +598,7 @@ take longer for you to get a helpful answer. Since as a user of lxml you are likely a programmer, you might find `this article on bug reports`_ an interesting read. -.. _`mailing list`: http://codespeak.net/mailman/listinfo/lxml-dev +.. _`mailing list`: http://lxml.de/mailinglist/ .. _`this article on bug reports`: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html diff --git a/doc/build.txt b/doc/build.txt index 3791b85d3..140720b89 100644 --- a/doc/build.txt +++ b/doc/build.txt @@ -157,7 +157,7 @@ like to know. Please contact us on the `mailing list`_, and please specify the version of lxml, libxml2, libxslt and Python you were using, as well as your operating system type (Linux, Windows, MacOs, ...). -.. _`mailing list`: http://codespeak.net/mailman/listinfo/lxml-dev +.. _`mailing list`: http://lxml.de/mailinglist/ Building an egg @@ -315,7 +315,7 @@ Building Debian packages from SVN sources `Andreas Pakulat`_ proposed the following approach. -.. _`Andreas Pakulat`: http://codespeak.net/pipermail/lxml-dev/2006-May/001254.html +.. _`Andreas Pakulat`: http://thread.gmane.org/gmane.comp.python.lxml.devel/1239/focus=1249 * ``apt-get source lxml`` * remove the unpacked directory diff --git a/doc/capi.txt b/doc/capi.txt index 4b9c8089c..d25807620 100644 --- a/doc/capi.txt +++ b/doc/capi.txt @@ -9,8 +9,8 @@ without going through the Python API. The API is described in the file `etreepublic.pxd`_, which is directly c-importable by extension modules implemented in Pyrex_ or Cython_. -.. _`etreepublic.pxd`: http://codespeak.net/svn/lxml/trunk/src/lxml/etreepublic.pxd -.. _Cython: http://www.cython.org +.. _`etreepublic.pxd`: https://github.com/lxml/lxml/blob/master/src/lxml/etreepublic.pxd +.. _Cython: http://cython.org .. _Pyrex: http://www.cosc.canterbury.ac.nz/~greg/python/Pyrex/ .. contents:: diff --git a/doc/lxml-source-howto.txt b/doc/lxml-source-howto.txt index 16e765ac2..2582d11b5 100644 --- a/doc/lxml-source-howto.txt +++ b/doc/lxml-source-howto.txt @@ -13,7 +13,7 @@ This document describes how to read the source code of lxml_ and how to start working on it. You might also be interested in the companion document that describes `how to build lxml from sources`_. -.. _lxml: http://codespeak.net/lxml/ +.. _lxml: http://lxml.de/ .. _`how to build lxml from sources`: build.html .. _`ReStructured Text`: http://docutils.sourceforge.net/rst.html .. _epydoc: http://epydoc.sourceforge.net/ @@ -154,7 +154,7 @@ lxml.etree ========== The main module, ``lxml.etree``, is in the file `lxml.etree.pyx -`_. It +`_. It implements the main functions and types of the ElementTree API, as well as all the factory functions for proxies. It is the best place to start if you want to find out how a specific feature is @@ -303,7 +303,7 @@ lxml.objectify A Cython implemented extension module that uses the public C-API of lxml.etree. It provides a Python object-like interface to XML trees. The implementation resides in the file `lxml.objectify.pyx -`_. +`_. lxml.html diff --git a/doc/lxmlhtml.txt b/doc/lxmlhtml.txt index ce6d9624a..776a4ae35 100644 --- a/doc/lxmlhtml.txt +++ b/doc/lxmlhtml.txt @@ -465,7 +465,7 @@ Example: >>> from lxml.html import parse, submit_form >>> page = parse('http://tinyurl.com').getroot() - >>> page.forms[1].fields['url'] = 'http://codespeak.net/lxml/' + >>> page.forms[1].fields['url'] = 'http://lxml.de/' >>> result = parse(submit_form(page.forms[1])).getroot() >>> [a.attrib['href'] for a in result.xpath("//a[@target='_blank']")] ['http://tinyurl.com/2xae8s', 'http://preview.tinyurl.com/2xae8s'] diff --git a/doc/performance.txt b/doc/performance.txt index 2f03b57f8..efde1a25c 100644 --- a/doc/performance.txt +++ b/doc/performance.txt @@ -98,9 +98,9 @@ platform. Note that many of the following ElementTree timings are therefore better then what a normal Python installation with the standard library (c)ElementTree modules would yield. -.. _`bench_etree.py`: http://codespeak.net/svn/lxml/trunk/benchmark/bench_etree.py -.. _`bench_xpath.py`: http://codespeak.net/svn/lxml/trunk/benchmark/bench_xpath.py -.. _`bench_objectify.py`: http://codespeak.net/svn/lxml/trunk/benchmark/bench_objectify.py +.. _`bench_etree.py`: https://github.com/lxml/lxml/blob/master/benchmark/bench_etree.py +.. _`bench_xpath.py`: https://github.com/lxml/lxml/blob/master/benchmark/bench_xpath.py +.. _`bench_objectify.py`: https://github.com/lxml/lxml/blob/master/benchmark/bench_objectify.py The scripts run a number of simple tests on the different libraries, using different XML tree configurations: different tree sizes (T1-4), with or