From eee933ed8482cb4c2fd963ff5e657b237bfb9ee1 Mon Sep 17 00:00:00 2001 From: venaturum Date: Fri, 23 Sep 2022 15:58:32 +1000 Subject: [PATCH] minor changes in dependency spec example --- docs/dependency-specification.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/dependency-specification.md b/docs/dependency-specification.md index b55b4710790..b841d68bc10 100644 --- a/docs/dependency-specification.md +++ b/docs/dependency-specification.md @@ -301,15 +301,15 @@ pathlib2 = { version = "^2.2", markers = "python_version <= '3.4' or sys_platfor Sometimes, one of your dependency may have different version ranges depending on the target Python versions. -Let’s say you have a dependency on the package foo which is only compatible -with Python >=3.6,<3.8 up to version 1.9 and compatible with Python 3.8+ from version 2.0: +Let's say you have a dependency on the package `foo` which is only compatible +with Python 3.6-3.7 up to version 1.9, and compatible with Python 3.8+ from version 2.0: you would declare it like so: ```toml [tool.poetry.dependencies] foo = [ - {version = "<=1.9", python = "^3.6"}, - {version = "^2.0", python = "^3.8"} + {version = "<=1.9", python = ">=3.6,<3.8"}, + {version = "^2.0", python = ">=3.8"} ] ```