Merge pull request #1411 from opensafely/steve/fix-python-docker-links

Fix links to Python Docker image

docs/actions-reusable.md

@@ -81,7 +81,7 @@ if __name__ == "__main__":
 When developing a reusable action, just as when developing a scripted action, the action's dependencies are made available by the runtime; they are not made available by the action.
 
 * The Python runtime is provided by [`python-docker`](https://github.com/opensafely-core/python-docker).
-  Its dependencies are in [*requirements.txt*](https://github.com/opensafely-core/python-docker/blob/main/requirements.txt).
+  Its dependencies are in [*requirements.txt*](https://github.com/opensafely-core/python-docker/blob/main/v1/requirements.txt).
   In practice, this means that a Python action's *requirements.txt* is ignored.
 * The R runtime is provided by [`r-docker`](https://github.com/opensafely-core/r-docker).
   Its dependencies are in [*packages.csv*](https://github.com/opensafely-core/r-docker/blob/master/packages.csv).

docs/actions-scripts.md

@@ -34,7 +34,7 @@ Scripted actions can read and write output files that are saved in the workspace
 
 Outputs labelled `highly_sensitive` will not be visible to researchers. This is a [deliberate design feature of OpenSAFELY](https://www.opensafely.org/about/), intended to reduce the risk of disclosure of sensitive information. Outputs should **always** be classed as `highly_sensitive` if they are:
 
-- Pseudonymised patient-level outputs derived from queries run against Level 1 and 2 data, i.e., a specific study dataset generated by a [dataset_definition](https://docs.opensafely.org/ehrql/).
+- Pseudonymised patient-level outputs derived from queries run against Level 1 and 2 data, i.e., a specific study dataset generated by a [dataset definition](ehrql/index.md).
 - Pseudonymised patient-level intermediate outputs for a study derived from queries run against Level 3 data which output pseudonymised patient-level data i.e., a processed study dataset with certain filters/formatting applied.
 
 These types of outputs are considered potentially highly-disclosive, should not be pushed to Level 4, and are never intended for publishing outside the secure environment.
@@ -168,7 +168,7 @@ The `opensafely` command line software will now automatically use this Stata lic
 
 ### Python
 
-The Docker image provided is Python 3.8, with [this list of packages installed](https://github.com/opensafely-core/python-docker/blob/main/requirements.txt).
+The Docker image provided is Python 3.8, with [this list of packages installed](https://github.com/opensafely-core/python-docker/blob/main/v1/requirements.txt).
 
 ### R
 

docs/requesting-libraries.md

@@ -36,7 +36,7 @@ issue](https://github.com/opensafely-core/stata-docker/issues) to request the pa
 
 ## Python packages
 
-First check that the package is not already available, by [viewing all installed packages and their versions for the OpenSAFELY Python image](https://github.com/opensafely-core/python-docker/blob/main/requirements.in). If your package isn't there then [open an
+First check that the package is not already available, by [viewing all installed packages and their versions for the OpenSAFELY Python image](https://github.com/opensafely-core/python-docker/blob/main/v1/requirements.txt). If your package isn't there then [open an
 issue](https://github.com/opensafely-core/python-docker/issues) to request it be added. Include the following information:
 
 * A link to information about the package;