Author: Armin Rigo <[email protected]>
Branch:
Changeset: r70462:4c3f06367a60
Date: 2014-04-05 09:38 +0200
http://bitbucket.org/pypy/pypy/changeset/4c3f06367a60/
Log: Merged in groggi/pypy/latest-improve-doc (pull request #224)
PyPy Docs: fighting broken links #2
diff --git a/pypy/doc/cleanup.rst b/pypy/doc/cleanup.rst
--- a/pypy/doc/cleanup.rst
+++ b/pypy/doc/cleanup.rst
@@ -9,9 +9,3 @@
distribution.rst
- dot-net.rst
-
-
-
-
-
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
@@ -742,9 +742,9 @@
Testing modules in ``lib_pypy/``
--------------------------------
-You can go to the `lib_pypy/pypy_test/`_ directory and invoke the testing tool
+You can go to the `pypy/module/test_lib_pypy/`_ directory and invoke the
testing tool
("py.test" or "python ../../pypy/test_all.py") to run tests against the
-lib_pypy hierarchy. Note, that tests in `lib_pypy/pypy_test/`_ are allowed
+lib_pypy hierarchy. Note, that tests in `pypy/module/test_lib_pypy/`_ are
allowed
and encouraged to let their tests run at interpreter level although
`lib_pypy/`_ modules eventually live at PyPy's application level.
This allows us to quickly test our python-coded reimplementations
@@ -835,15 +835,6 @@
web interface.
.. _`development tracker`: https://bugs.pypy.org/
-
-use your codespeak login or register
-------------------------------------
-
-If you have an existing codespeak account, you can use it to login within the
-tracker. Else, you can `register with the tracker`_ easily.
-
-
-.. _`register with the tracker`: https://bugs.pypy.org/user?@template=register
.. _`roundup`: http://roundup.sourceforge.net/
diff --git a/pypy/doc/config/opt.rst b/pypy/doc/config/opt.rst
--- a/pypy/doc/config/opt.rst
+++ b/pypy/doc/config/opt.rst
@@ -46,5 +46,5 @@
The default level is `2`.
-.. _`Boehm-Demers-Weiser garbage collector`:
http://www.hpl.hp.com/personal/Hans_Boehm/gc/
+.. _`Boehm-Demers-Weiser garbage collector`: http://hboehm.info/gc/
.. _`custom garbage collectors`: ../garbage_collection.html
diff --git a/pypy/doc/config/translation.backendopt.txt
b/pypy/doc/config/translation.backendopt.txt
--- a/pypy/doc/config/translation.backendopt.txt
+++ b/pypy/doc/config/translation.backendopt.txt
@@ -1,5 +1,5 @@
This group contains options about various backend optimization passes. Most of
them are described in the `EU report about optimization`_
-.. _`EU report about optimization`:
http://codespeak.net/pypy/extradoc/eu-report/D07.1_Massive_Parallelism_and_Translation_Aspects-2007-02-28.pdf
+.. _`EU report about optimization`:
https://bitbucket.org/pypy/extradoc/raw/tip/eu-report/D07.1_Massive_Parallelism_and_Translation_Aspects-2007-02-28.pdf
diff --git a/pypy/doc/discussions.rst b/pypy/doc/discussions.rst
--- a/pypy/doc/discussions.rst
+++ b/pypy/doc/discussions.rst
@@ -11,7 +11,5 @@
discussion/finalizer-order.rst
discussion/howtoimplementpickling.rst
discussion/improve-rpython.rst
- discussion/outline-external-ootype.rst
- discussion/VM-integration.rst
diff --git a/pypy/doc/distribution.rst b/pypy/doc/distribution.rst
--- a/pypy/doc/distribution.rst
+++ b/pypy/doc/distribution.rst
@@ -1,5 +1,3 @@
-.. include:: needswork.txt
-
=============================
lib_pypy/distributed features
=============================
diff --git a/pypy/doc/eventhistory.rst b/pypy/doc/eventhistory.rst
--- a/pypy/doc/eventhistory.rst
+++ b/pypy/doc/eventhistory.rst
@@ -17,7 +17,7 @@
Read more in the `EuroPython 2006 sprint report`_.
-.. _`EuroPython 2006 sprint report`:
http://codespeak.net/pypy/extradoc/sprintinfo/post-ep2006/report.txt
+.. _`EuroPython 2006 sprint report`:
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/post-ep2006/report.txt
PyPy at XP 2006 and Agile 2006
==================================================================
@@ -41,8 +41,8 @@
Read more in `the sprint announcement`_, see who is planning to attend
on the `people page`_.
-.. _`the sprint announcement`:
http://codespeak.net/pypy/extradoc/sprintinfo/ddorf2006/announce.html
-.. _`people page`:
http://codespeak.net/pypy/extradoc/sprintinfo/ddorf2006/people.html
+.. _`the sprint announcement`:
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/ddorf2006/announce.html
+.. _`people page`:
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/ddorf2006/people.txt
PyPy sprint at Akihabara (Tokyo, Japan)
==================================================================
@@ -84,8 +84,8 @@
Read the report_ and the original announcement_.
-.. _report:
http://codespeak.net/pypy/extradoc/sprintinfo/louvain-la-neuve-2006/report.html
-.. _announcement:
http://codespeak.net/pypy/extradoc/sprintinfo/louvain-la-neuve-2006/sprint-announcement.html
+.. _report:
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/louvain-la-neuve-2006/report.txt
+.. _announcement:
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/louvain-la-neuve-2006/sprint-announcement.txt
PyCon Sprint 2006 (Dallas, Texas, USA)
==================================================================
@@ -114,7 +114,7 @@
said they were interested in the outcome and would keep an eye on its
progress. Read the `talk slides`_.
-.. _`talk slides`:
http://codespeak.net/pypy/extradoc/talk/solutions-linux-paris-2006.html
+.. _`talk slides`:
https://bitbucket.org/pypy/extradoc/raw/tip/talk/solutions-linux-paris-2006.html
PyPy Sprint in Palma De Mallorca 23rd - 29th January 2006
@@ -129,9 +129,9 @@
for the first three days and `one for the rest of the sprint`_.
-.. _`the announcement`:
http://codespeak.net/pypy/extradoc/sprintinfo/mallorca/sprint-announcement.html
-.. _`sprint report`:
http://codespeak.net/pipermail/pypy-dev/2006q1/002746.html
-.. _`one for the rest of the sprint`:
http://codespeak.net/pipermail/pypy-dev/2006q1/002749.html
+.. _`the announcement`:
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/mallorca/sprint-announcement.txt
+.. _`sprint report`:
https://mail.python.org/pipermail/pypy-dev/2006-January/002746.html
+.. _`one for the rest of the sprint`:
https://mail.python.org/pipermail/pypy-dev/2006-January/002749.html
Preliminary EU reports released
===============================
@@ -155,8 +155,8 @@
Michael and Carl have written a `report about the first half`_ and `one about
the second half`_ of the sprint. *(12/18/2005)*
-.. _`report about the first half`:
http://codespeak.net/pipermail/pypy-dev/2005q4/002656.html
-.. _`one about the second half`:
http://codespeak.net/pipermail/pypy-dev/2005q4/002660.html
+.. _`report about the first half`:
https://mail.python.org/pipermail/pypy-dev/2005-December/002656.html
+.. _`one about the second half`:
https://mail.python.org/pipermail/pypy-dev/2005-December/002660.html
PyPy release 0.8.0
===================
@@ -187,12 +187,12 @@
way back.
*(10/18/2005)*
-.. _`Logilab offices in Paris`:
http://codespeak.net/pypy/extradoc/sprintinfo/paris-2005-sprint.html
+.. _`Logilab offices in Paris`:
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/paris-2005-sprint.txt
.. _JIT: http://en.wikipedia.org/wiki/Just-in-time_compilation
.. _`continuation-passing`:
http://en.wikipedia.org/wiki/Continuation_passing_style
-.. _`report about day one`:
http://codespeak.net/pipermail/pypy-dev/2005q4/002510.html
-.. _`one about day two and three`:
http://codespeak.net/pipermail/pypy-dev/2005q4/002512.html
-.. _`the rest of the sprint`:
http://codespeak.net/pipermail/pypy-dev/2005q4/002514.html
+.. _`report about day one`:
https://mail.python.org/pipermail/pypy-dev/2005-October/002510.html
+.. _`one about day two and three`:
https://mail.python.org/pipermail/pypy-dev/2005-October/002512.html
+.. _`the rest of the sprint`:
https://mail.python.org/pipermail/pypy-dev/2005-October/002514.html
PyPy release 0.7.0
===================
@@ -217,15 +217,13 @@
Its main focus is translation of the whole PyPy interpreter
to a low level language and reaching 2.4.1 Python compliance.
The goal of the sprint is to release a first self-contained
-PyPy-0.7 version. Carl has written a report about `day 1 - 3`_,
-there are `some pictures`_ online and a `heidelberg summary report`_
-detailing some of the works that led to the successful release
-of `pypy-0.7.0`_!
+PyPy-0.7 version. Carl has written a report about `day 1 - 3`_
+and a `heidelberg summary report`_ detailing some of the works
+that led to the successful release of `pypy-0.7.0`_!
-.. _`heidelberg summary report`:
http://codespeak.net/pypy/extradoc/sprintinfo/Heidelberg-report.html
-.. _`PyPy sprint`:
http://codespeak.net/pypy/extradoc/sprintinfo/Heidelberg-sprint.html
-.. _`day 1 - 3`: http://codespeak.net/pipermail/pypy-dev/2005q3/002287.html
-.. _`some pictures`: http://codespeak.net/~hpk/heidelberg-sprint/
+.. _`heidelberg summary report`:
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/Heidelberg-report.txt
+.. _`PyPy sprint`:
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/Heidelberg-sprint.txt
+.. _`day 1 - 3`:
https://mail.python.org/pipermail/pypy-dev/2005-August/002287.html
PyPy Hildesheim2 finished: first self-contained PyPy run!
===========================================================
@@ -233,20 +231,16 @@
Up until 31st August we were in a PyPy sprint at `Trillke-Gut`_.
Carl has written a `report about day 1`_, Holger
about `day 2 and day 3`_ and Carl again about `day 4 and day 5`_,
-On `day 6`_ Holger reports the `breakthrough`_: PyPy runs
-on its own! Hurray_!. And Carl finally reports about the winding
+On `day 6`_ Holger reports the breakthrough: PyPy runs
+on its own! Hurray!. And Carl finally reports about the winding
down of `day 7`_ which saw us relaxing, discussing and generally
-having a good time. You might want to look at the selected
-`pictures from the sprint`_.
+having a good time.
-.. _`report about day 1`:
http://codespeak.net/pipermail/pypy-dev/2005q3/002217.html
-.. _`day 2 and day 3`:
http://codespeak.net/pipermail/pypy-dev/2005q3/002220.html
-.. _`day 4 and day 5`:
http://codespeak.net/pipermail/pypy-dev/2005q3/002234.html
-.. _`day 6`: http://codespeak.net/pipermail/pypy-dev/2005q3/002239.html
-.. _`day 7`: http://codespeak.net/pipermail/pypy-dev/2005q3/002245.html
-.. _`breakthrough`:
http://codespeak.net/~hpk/hildesheim2-sprint-www/hildesheim2-sprint-www-Thumbnails/36.jpg
-.. _`hurray`:
http://codespeak.net/~hpk/hildesheim2-sprint-www/hildesheim2-sprint-www-Pages/Image37.html
-.. _`pictures from the sprint`:
http://codespeak.net/~hpk/hildesheim2-sprint-www/
+.. _`report about day 1`:
https://mail.python.org/pipermail/pypy-dev/2005-July/002217.html
+.. _`day 2 and day 3`:
https://mail.python.org/pipermail/pypy-dev/2005-July/002220.html
+.. _`day 4 and day 5`:
https://mail.python.org/pipermail/pypy-dev/2005-July/002234.html
+.. _`day 6`: https://mail.python.org/pipermail/pypy-dev/2005-July/002239.html
+.. _`day 7`: https://mail.python.org/pipermail/pypy-dev/2005-August/002245.html
.. _`Trillke-Gut`: http://www.trillke.net
EuroPython 2005 sprints finished
@@ -264,15 +258,15 @@
the LLVM backends and type inference in general.
*(07/13/2005)*
-.. _`day 1`: http://codespeak.net/pipermail/pypy-dev/2005q2/002169.html
-.. _`day 2`: http://codespeak.net/pipermail/pypy-dev/2005q2/002171.html
-.. _`day 3`: http://codespeak.net/pipermail/pypy-dev/2005q2/002172.html
-.. _`pypy-dev`: http://mail.python.org/mailman/listinfo/pypy-dev
+.. _`day 1`: https://mail.python.org/pipermail/pypy-dev/2005-June/002169.html
+.. _`day 2`: https://mail.python.org/pipermail/pypy-dev/2005-June/002171.html
+.. _`day 3`: https://mail.python.org/pipermail/pypy-dev/2005-June/002172.html
+.. _`pypy-dev`: https://mail.python.org/mailman/listinfo/pypy-dev
.. _EuroPython: http://europython.org
.. _`translation`: translation.html
-.. _`sprint announcement`:
http://codespeak.net/pypy/extradoc/sprintinfo/EP2005-announcement.html
-.. _`list of people coming`:
http://codespeak.net/pypy/extradoc/sprintinfo/EP2005-people.html
+.. _`sprint announcement`:
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/EP2005-announcement.html
+.. _`list of people coming`:
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/EP2005-people.html
Duesseldorf PyPy sprint 2-9 June 2006
==================================================================
@@ -285,8 +279,8 @@
Read more in `the sprint announcement`_, see who is planning to attend
on the `people page`_.
-.. _`the sprint announcement`:
http://codespeak.net/pypy/extradoc/sprintinfo/ddorf2006/announce.html
-.. _`people page`:
http://codespeak.net/pypy/extradoc/sprintinfo/ddorf2006/people.html
+.. _`the sprint announcement`:
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/ddorf2006/announce.txt
+.. _`people page`:
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/ddorf2006/people.txt
PyPy at XP 2006 and Agile 2006
diff --git a/pypy/doc/extradoc.rst b/pypy/doc/extradoc.rst
--- a/pypy/doc/extradoc.rst
+++ b/pypy/doc/extradoc.rst
@@ -79,7 +79,7 @@
.. _`Tracing the Meta-Level: PyPy's Tracing JIT Compiler`:
https://bitbucket.org/pypy/extradoc/raw/tip/talk/icooolps2009/bolz-tracing-jit.pdf
.. _`Faster than C#: Efficient Implementation of Dynamic Languages on .NET`:
https://bitbucket.org/pypy/extradoc/raw/tip/talk/icooolps2009-dotnet/cli-jit.pdf
.. _`Automatic JIT Compiler Generation with Runtime Partial Evaluation`:
http://wwwold.cobra.cs.uni-duesseldorf.de/thesis/final-master.pdf
-.. _`RPython: A Step towards Reconciling Dynamically and Statically Typed OO
Languages`:
http://www.disi.unige.it/person/AnconaD/papers/Recent_abstracts.html#AACM-DLS07
+.. _`RPython: A Step towards Reconciling Dynamically and Statically Typed OO
Languages`:
http://www.disi.unige.it/person/AnconaD/papers/DynamicLanguages_abstracts.html#AACM-DLS07
.. _`EU Reports`: index-report.html
.. _`Hardware Transactional Memory Support for Lightweight Dynamic Language
Evolution`: http://sabi.net/nriley/pubs/dls6-riley.pdf
.. _`PyGirl: Generating Whole-System VMs from High-Level Prototypes using
PyPy`: http://scg.unibe.ch/archive/papers/Brun09cPyGirl.pdf
@@ -356,8 +356,6 @@
.. _`transparent dynamic optimization`:
http://www.hpl.hp.com/techreports/1999/HPL-1999-77.pdf
.. _Dynamo: http://www.hpl.hp.com/techreports/1999/HPL-1999-78.pdf
.. _testdesign: coding-guide.html#test-design
-.. _feasible: http://codespeak.net/pipermail/pypy-dev/2004q2/001289.html
-.. _rock: http://codespeak.net/pipermail/pypy-dev/2004q1/001255.html
.. _LLVM: http://llvm.org/
.. _IronPython: http://ironpython.codeplex.com/
.. _`Dynamic Native Optimization of Native Interpreters`:
http://people.csail.mit.edu/gregs/dynamorio.html
diff --git a/pypy/doc/getting-started-dev.rst b/pypy/doc/getting-started-dev.rst
--- a/pypy/doc/getting-started-dev.rst
+++ b/pypy/doc/getting-started-dev.rst
@@ -222,7 +222,7 @@
PyPy development always was and is still thoroughly test-driven.
We use the flexible `py.test testing tool`_ which you can `install
independently
-<http://pytest.org/getting-started.html>`_ and use for other projects.
+<http://pytest.org/latest/getting-started.html#getstarted>`_ and use for other
projects.
The PyPy source tree comes with an inlined version of ``py.test``
which you can invoke by typing::
@@ -264,7 +264,7 @@
interpreter.
.. _`py.test testing tool`: http://pytest.org
-.. _`py.test usage and invocations`: http://pytest.org/usage.html#usage
+.. _`py.test usage and invocations`: http://pytest.org/latest/usage.html#usage
Special Introspection Features of the Untranslated Python Interpreter
---------------------------------------------------------------------
diff --git a/pypy/doc/glossary.rst b/pypy/doc/glossary.rst
--- a/pypy/doc/glossary.rst
+++ b/pypy/doc/glossary.rst
@@ -1,5 +1,3 @@
-.. include:: needswork.txt
-
.. _glossary:
********
diff --git a/pypy/doc/interpreter.rst b/pypy/doc/interpreter.rst
--- a/pypy/doc/interpreter.rst
+++ b/pypy/doc/interpreter.rst
@@ -256,7 +256,7 @@
example and the higher level `chapter on Modules in the coding
guide`_.
-.. _`__builtin__ module`:
https://bitbucket.org/pypy/pypy/src/tip/pypy/module/__builtin__/
+.. _`__builtin__ module`:
https://bitbucket.org/pypy/pypy/src/default/pypy/module/__builtin__/
.. _`chapter on Modules in the coding guide`: coding-guide.html#modules
.. _`Gateway classes`:
diff --git a/pypy/doc/objspace-proxies.rst b/pypy/doc/objspace-proxies.rst
--- a/pypy/doc/objspace-proxies.rst
+++ b/pypy/doc/objspace-proxies.rst
@@ -185,6 +185,6 @@
.. _`standard object space`: objspace.html#the-standard-object-space
.. [D12.1] `High-Level Backends and Interpreter Feature Prototypes`, PyPy
- EU-Report, 2007,
http://codespeak.net/pypy/extradoc/eu-report/D12.1_H-L-Backends_and_Feature_Prototypes-2007-03-22.pdf
+ EU-Report, 2007,
https://bitbucket.org/pypy/extradoc/raw/tip/eu-report/D12.1_H-L-Backends_and_Feature_Prototypes-2007-03-22.pdf
.. include:: _ref.txt
diff --git a/pypy/doc/objspace.rst b/pypy/doc/objspace.rst
--- a/pypy/doc/objspace.rst
+++ b/pypy/doc/objspace.rst
@@ -348,15 +348,15 @@
* the *implementation* module, called ``xxxobject.py``.
The ``xxxtype.py`` module basically defines the type object itself. For
-example, `pypy/objspace/std/listtype.py`_ contains the specification of the
object you get when
-you type ``list`` in a PyPy prompt. `pypy/objspace/std/listtype.py`_
enumerates the methods
+example, `pypy/objspace/std/listobject.py`_ contains the specification of the
object you get when
+you type ``list`` in a PyPy prompt. `pypy/objspace/std/listobject.py`_
enumerates the methods
specific to lists, like ``append()``.
A particular method implemented by all types is the ``__new__()`` special
method, which in Python's new-style-classes world is responsible for creating
an instance of the type. In PyPy, ``__new__()`` locates and imports the module
implementing *instances* of the type, and creates such an instance based on the
-arguments the user supplied to the constructor. For example,
`pypy/objspace/std/tupletype.py`_
+arguments the user supplied to the constructor. For example,
`pypy/objspace/std/tupleobject.py`_
defines ``__new__()`` to import the class ``W_TupleObject`` from
`pypy/objspace/std/tupleobject.py`_ and instantiate it. The
`pypy/objspace/std/tupleobject.py`_ then contains a
"real" implementation of tuples: the way the data is stored in the
@@ -374,9 +374,9 @@
same Python type. PyPy knows that (e.g.) the application-level type of
its interpreter-level ``W_StringObject`` instances is str because
there is a ``typedef`` class attribute in ``W_StringObject`` which
-points back to the string type specification from
`pypy/objspace/std/stringtype.py`_; all
+points back to the string type specification from
`pypy/objspace/std/stringobject.py`_; all
other implementations of strings use the same ``typedef`` from
-`pypy/objspace/std/stringtype.py`_.
+`pypy/objspace/std/stringobject.py`_.
For other examples of multiple implementations of the same Python type,
see `Standard Interpreter Optimizations`_.
@@ -491,7 +491,7 @@
Introduction
------------
-The task of the FlowObjSpace (the source is at `pypy/objspace/flow/`_) is to
generate a control-flow graph from a
+The task of the FlowObjSpace (the source is at `rpython/flowspace/`_) is to
generate a control-flow graph from a
function. This graph will also contain a trace of the individual operations,
so
that it is actually just an alternate representation for the function.
diff --git a/pypy/doc/rffi.rst b/pypy/doc/rffi.rst
--- a/pypy/doc/rffi.rst
+++ b/pypy/doc/rffi.rst
@@ -43,7 +43,7 @@
See cbuild_ for more info on ExternalCompilationInfo.
.. _`low level types`: rtyper.html#low-level-type
-.. _cbuild:
https://bitbucket.org/pypy/pypy/src/tip/rpython/translator/tool/cbuild.py
+.. _cbuild:
https://bitbucket.org/pypy/pypy/src/default/rpython/translator/tool/cbuild.py
Types
@@ -56,7 +56,7 @@
flavor='raw'. There are several helpers like string -> char*
converter, refer to the source for details.
-.. _rffi:
https://bitbucket.org/pypy/pypy/src/tip/pypy/rpython/lltypesystem/rffi.py
+.. _rffi:
https://bitbucket.org/pypy/pypy/src/default/rpython/rtyper/lltypesystem/rffi.py
Registering function as external
---------------------------------
@@ -68,4 +68,4 @@
functions, passing llimpl as an argument and eventually llfakeimpl
as a fake low-level implementation for tests performed by an llinterp.
-.. _`extfunc.py`:
https://bitbucket.org/pypy/pypy/src/tip/pypy/rpython/extfunc.py
+.. _`extfunc.py`:
https://bitbucket.org/pypy/pypy/src/default/rpython/rtyper/extfunc.py
diff --git a/pypy/doc/sprint-reports.rst b/pypy/doc/sprint-reports.rst
--- a/pypy/doc/sprint-reports.rst
+++ b/pypy/doc/sprint-reports.rst
@@ -42,30 +42,30 @@
* `CERN (July 2010)`_
* `Düsseldorf (October 2010)`_
- .. _Hildesheim (Feb 2003):
http://codespeak.net/pypy/extradoc/sprintinfo/HildesheimReport.html
- .. _Gothenburg (May 2003):
http://codespeak.net/pypy/extradoc/sprintinfo/gothenburg-2003-sprintreport.txt
- .. _LovainLaNeuve (June 2003):
http://codespeak.net/pypy/extradoc/sprintinfo/LouvainLaNeuveReport.txt
- .. _Berlin (Sept 2003):
http://codespeak.net/pypy/extradoc/sprintinfo/BerlinReport.txt
- .. _Amsterdam (Dec 2003):
http://codespeak.net/pypy/extradoc/sprintinfo/AmsterdamReport.txt
- .. _Vilnius (Nov 2004):
http://codespeak.net/pypy/extradoc/sprintinfo/vilnius-2004-sprintreport.txt
- .. _Leysin (Jan 2005):
http://codespeak.net/pypy/extradoc/sprintinfo/LeysinReport.txt
- .. _PyCon/Washington (March 2005):
http://codespeak.net/pypy/extradoc/sprintinfo/pycon_sprint_report.txt
- .. _Europython/Gothenburg (June 2005):
http://codespeak.net/pypy/extradoc/sprintinfo/ep2005-sprintreport.txt
- .. _Hildesheim (July 2005):
http://codespeak.net/pypy/extradoc/sprintinfo/hildesheim2005-sprintreport.txt
- .. _Heidelberg (Aug 2005):
http://codespeak.net/pypy/extradoc/sprintinfo/Heidelberg-report.txt
- .. _Paris (Oct 2005):
http://codespeak.net/pypy/extradoc/sprintinfo/paris/paris-report.txt
- .. _Gothenburg (Dec 2005):
http://codespeak.net/pypy/extradoc/sprintinfo/gothenburg-2005/gothenburg-dec2005-sprintreport.txt
- .. _Mallorca (Jan 2006):
http://codespeak.net/pypy/extradoc/sprintinfo/mallorca/mallorca-sprintreport.txt
- .. _LouvainLaNeuve (March 2006):
http://codespeak.net/pypy/extradoc/sprintinfo/louvain-la-neuve-2006/report.txt
- .. _Leysin (April 2006):
http://codespeak.net/pypy/extradoc/sprintinfo/leysin-winter-2006-sprintreport.txt
- .. _Tokyo (April 2006):
http://codespeak.net/pypy/extradoc/sprintinfo/tokyo/sprint-report.txt
- .. _Düsseldorf (June 2006):
http://codespeak.net/pypy/extradoc/sprintinfo/ddorf2006/report1.txt
- .. _Europython/Geneva (July 2006):
http://codespeak.net/pypy/extradoc/sprintinfo/post-ep2006/report.txt
- .. _Düsseldorf (October 2006):
http://codespeak.net/pypy/extradoc/sprintinfo/ddorf2006b/report.txt
- .. _`Leysin (January 2007)`:
http://codespeak.net/pypy/extradoc/sprintinfo/leysin-winter-2007/report.txt
- .. _Hildesheim (Feb 2007):
http://codespeak.net/pypy/extradoc/sprintinfo/trillke-2007/sprint-report.txt
- .. _`EU report writing sprint`:
http://codespeak.net/pypy/extradoc/sprintinfo/trillke-2007/eu-report-sprint-report.txt
- .. _`PyCon/Dallas (Feb 2006)`:
http://codespeak.net/pypy/extradoc/sprintinfo/pycon06/sprint-report.txt
+ .. _Hildesheim (Feb 2003):
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/HildesheimReport.txt
+ .. _Gothenburg (May 2003):
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/gothenburg-2003-sprintreport.txt
+ .. _LovainLaNeuve (June 2003):
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/LouvainLaNeuveReport.txt
+ .. _Berlin (Sept 2003):
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/BerlinReport.txt
+ .. _Amsterdam (Dec 2003):
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/AmsterdamReport.txt
+ .. _Vilnius (Nov 2004):
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/vilnius-2004-sprintreport.txt
+ .. _Leysin (Jan 2005):
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/LeysinReport.txt
+ .. _PyCon/Washington (March 2005):
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/pycon_sprint_report.txt
+ .. _Europython/Gothenburg (June 2005):
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/ep2005-sprintreport.txt
+ .. _Hildesheim (July 2005):
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/hildesheim2005-sprintreport.txt
+ .. _Heidelberg (Aug 2005):
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/Heidelberg-report.txt
+ .. _Paris (Oct 2005):
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/paris/paris-report.txt
+ .. _Gothenburg (Dec 2005):
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/gothenburg-2005/gothenburg-dec2005-sprintreport.txt
+ .. _Mallorca (Jan 2006):
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/mallorca/mallorca-sprintreport.txt
+ .. _LouvainLaNeuve (March 2006):
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/louvain-la-neuve-2006/report.txt
+ .. _Leysin (April 2006):
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/leysin-winter-2006-sprintreport.txt
+ .. _Tokyo (April 2006):
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/tokyo/sprint-report.txt
+ .. _Düsseldorf (June 2006):
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/ddorf2006/report1.txt
+ .. _Europython/Geneva (July 2006):
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/post-ep2006/report.txt
+ .. _Düsseldorf (October 2006):
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/ddorf2006b/report.txt
+ .. _`Leysin (January 2007)`:
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/leysin-winter-2007/report.txt
+ .. _Hildesheim (Feb 2007):
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/trillke-2007/sprint-report.txt
+ .. _`EU report writing sprint`:
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/trillke-2007/eu-report-sprint-report.txt
+ .. _`PyCon/Dallas (Feb 2006)`:
https://bitbucket.org/pypy/extradoc/raw/tip/sprintinfo/pycon06/sprint-report.txt
.. _`Göteborg (November 2007)`:
http://morepypy.blogspot.com/2007_11_01_archive.html
.. _`Leysin (January 2008)`:
http://morepypy.blogspot.com/2008/01/leysin-winter-sport-sprint-started.html
.. _`Berlin (May 2008)`:
http://morepypy.blogspot.com/2008_05_01_archive.html
diff --git a/pypy/doc/statistic/index.rst b/pypy/doc/statistic/index.rst
--- a/pypy/doc/statistic/index.rst
+++ b/pypy/doc/statistic/index.rst
@@ -1,3 +1,7 @@
+.. warning::
+
+ This page is no longer updated, of historical interest only.
+
=======================
PyPy Project Statistics
=======================
diff --git a/pypy/doc/translation.rst b/pypy/doc/translation.rst
--- a/pypy/doc/translation.rst
+++ b/pypy/doc/translation.rst
@@ -380,7 +380,7 @@
The RPython Typer
=================
-https://bitbucket.org/pypy/pypy/src/default/pypy/rpython/
+https://bitbucket.org/pypy/pypy/src/default/rpython/rtyper/
The RTyper is the first place where the choice of backend makes a
difference; as outlined above we are assuming that ANSI C is the target.
@@ -603,7 +603,7 @@
- using the `Boehm-Demers-Weiser conservative garbage collector`_
- using one of our custom `exact GCs implemented in RPython`_
-.. _`Boehm-Demers-Weiser conservative garbage collector`:
http://www.hpl.hp.com/personal/Hans_Boehm/gc/
+.. _`Boehm-Demers-Weiser conservative garbage collector`:
http://hboehm.info/gc/
.. _`exact GCs implemented in RPython`: garbage_collection.html
Almost all application-level Python code allocates objects at a very fast
@@ -621,7 +621,7 @@
The C Back-End
==============
-https://bitbucket.org/pypy/pypy/src/default/pypy/translator/c/
+https://bitbucket.org/pypy/pypy/src/default/rpython/translator/c/
GenC is usually the most actively maintained backend -- everyone working on
PyPy has a C compiler, for one thing -- and is usually where new features are
diff --git a/pypy/doc/windows.rst b/pypy/doc/windows.rst
--- a/pypy/doc/windows.rst
+++ b/pypy/doc/windows.rst
@@ -86,7 +86,7 @@
option (this is the default at some optimization levels like ``-O1``,
but unneeded for high-performance translations like ``-O2``).
You may get it at
-http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc-7.1.tar.gz
+http://hboehm.info/gc/gc_source/gc-7.1.tar.gz
Versions 7.0 and 7.1 are known to work; the 6.x series won't work with
pypy. Unpack this folder in the base directory. Then open a command
_______________________________________________
pypy-commit mailing list
[email protected]
https://mail.python.org/mailman/listinfo/pypy-commit
