You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildstream.apache.org by tv...@apache.org on 2022/01/01 10:34:38 UTC

[buildstream] 02/07: doc/source/format_project.rst: Stop referring to broken link.

This is an automated email from the ASF dual-hosted git repository.

tvb pushed a commit to branch tristan/porting-guide
in repository https://gitbox.apache.org/repos/asf/buildstream.git

commit 0e16be24f41b1f94181c158777200919ba1246c0
Author: Tristan van Berkom <tr...@codethink.co.uk>
AuthorDate: Sat Jan 1 17:03:31 2022 +0900

    doc/source/format_project.rst: Stop referring to broken link.
    
    There used to be a good human readable document about versioning
    constraints at: https://python-poetry.org/docs/versions/
    
    But it's gone.
---
 doc/source/format_project.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/source/format_project.rst b/doc/source/format_project.rst
index 69b1e4c..dc089bf 100644
--- a/doc/source/format_project.rst
+++ b/doc/source/format_project.rst
@@ -389,8 +389,8 @@ When loading plugins from the ``pip`` plugin origin, it is possible to
 specify constraints on the versions of packages you want to load
 your plugins from.
 
-The syntax for specifying constraints are `explained here <https://python-poetry.org/docs/versions/>`_,
-and they are the same format supported by the ``pip`` package manager.
+The syntax for specifying versioning constraints is the same format supported by
+the ``pip`` package manager.
 
 .. note::