Skip to content

Commit ba9f79c

Browse files
fix poetry link
1 parent 972dbf2 commit ba9f79c

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

tutorials/pyproject-toml.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -351,7 +351,9 @@ Code changes over time, bugs are fixed, APIs change, and so it's good to be clea
351351
[Learn more about various ways to specify ranges of package versions here.](https://packaging.python.org/en/latest/specifications/version-specifiers/#id5)
352352

353353
The most common version specifier is a **lower bound,** allowing any version higher than the specified version.
354-
Ideally you should set this to the lowest version that is still compatible with your package, but in practice for new packages this is often set at the version that was current at the time the package was written.
354+
Ideally you should set this to the lowest version that is still compatible with your package, but in practice for new packages this is often set at the version that was current at the time the package was written[^lowerbound].
355+
356+
[^lowerbound]:
355357

356358
Lower bounds look like this:
357359

@@ -421,7 +423,7 @@ pydantic>=1.10,<2
421423
pydantic^1.10
422424
```
423425

424-
One build tool that you should be aware of that pins dependencies to an upper bound by default is Poetry. [Read more about how to safely add dependencies with Poetry, here.](../package-structure-code/python-package-build-tools.html#challenges-with-poetry)
426+
One build tool that you should be aware of that pins dependencies to an upper bound by default is Poetry. [Read more about how to safely add dependencies with Poetry, here.](challenges-with-poetry)
425427
:::
426428

427429
### Step 5: Add PyPI classifiers

0 commit comments

Comments
 (0)