From b21482a6b7232a7cf0f1b9c35a0ccfd0130dcc7b Mon Sep 17 00:00:00 2001 From: Stephan Renatus Date: Wed, 2 Nov 2022 10:04:20 +0100 Subject: [PATCH] docs/policy-testing: don't advise to "import future.keywords" Fixes #5333. Signed-off-by: Stephan Renatus --- docs/content/policy-testing.md | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/docs/content/policy-testing.md b/docs/content/policy-testing.md index 1cbbada33d..0bcf8eccc2 100644 --- a/docs/content/policy-testing.md +++ b/docs/content/policy-testing.md @@ -17,12 +17,8 @@ and reduce the amount of time it takes to modify rules as requirements evolve. {{< info >}} The examples in this section try to represent the best practices. As such, they make use of keywords that are meant to become standard keywords at some point in -time, but have been introduced gradually. These _future keywords_ can be enabled -using - -```live:eg/import:module:read_only -import future.keywords -``` +time, but have been introduced gradually. +[See the docs on _future keywords_](../policy-language/#future-keywords) for more information. {{< /info >}} ## Getting Started