Automatic deploy (build number 17)

conan-io · Mar 5, 2024 · 55518cf · 55518cf
1 parent 451b78b
commit 55518cf
Show file tree

Hide file tree

Showing 8 changed files with 10 additions and 6 deletions.
diff --git a/2.1/_sources/reference/extensions/python_requires.rst.txt b/2.1/_sources/reference/extensions/python_requires.rst.txt
@@ -313,7 +313,8 @@ There are few important things that should be taken into account when using ``py
 - Python requires are private to the consumers. They are not transitive. Different consumers
   can require different versions of the same ``python-require``. Being private, they cannot
   be overridden from downstream in any way.
-- ``python_requires`` cannot use regular ``requires`` or ``tool_requires``.
+- ``python_requires`` cannot use regular ``requires`` or ``tool_requires`` themselves. Having a ``requirements()`` (and similar)
+  methods to be inherited by recipes is possible and allowed, but the ``python_requires`` class itself cannot use them.
 - ``python_requires`` cannot be "aliased".
 - ``python_requires`` can use native python ``import`` to other python files, as long as these are
   exported together with the recipe.

diff --git a/2.1/conan.pdf b/2.1/conan.pdf
diff --git a/2.1/reference/extensions/python_requires.html b/2.1/reference/extensions/python_requires.html
@@ -387,7 +387,8 @@ <h2>Resolution of python_requires<a class="headerlink" href="#resolution-of-pyth
 <li><p>Python requires are private to the consumers. They are not transitive. Different consumers
 can require different versions of the same <code class="docutils literal notranslate"><span class="pre">python-require</span></code>. Being private, they cannot
 be overridden from downstream in any way.</p></li>
-<li><p><code class="docutils literal notranslate"><span class="pre">python_requires</span></code> cannot use regular <code class="docutils literal notranslate"><span class="pre">requires</span></code> or <code class="docutils literal notranslate"><span class="pre">tool_requires</span></code>.</p></li>
+<li><p><code class="docutils literal notranslate"><span class="pre">python_requires</span></code> cannot use regular <code class="docutils literal notranslate"><span class="pre">requires</span></code> or <code class="docutils literal notranslate"><span class="pre">tool_requires</span></code> themselves. Having a <code class="docutils literal notranslate"><span class="pre">requirements()</span></code> (and similar)
+methods to be inherited by recipes is possible and allowed, but the <code class="docutils literal notranslate"><span class="pre">python_requires</span></code> class itself cannot use them.</p></li>
 <li><p><code class="docutils literal notranslate"><span class="pre">python_requires</span></code> cannot be “aliased”.</p></li>
 <li><p><code class="docutils literal notranslate"><span class="pre">python_requires</span></code> can use native python <code class="docutils literal notranslate"><span class="pre">import</span></code> to other python files, as long as these are
 exported together with the recipe.</p></li>

diff --git a/2.1/searchindex.js b/2.1/searchindex.js
diff --git a/2/_sources/reference/extensions/python_requires.rst.txt b/2/_sources/reference/extensions/python_requires.rst.txt
@@ -313,7 +313,8 @@ There are few important things that should be taken into account when using ``py
 - Python requires are private to the consumers. They are not transitive. Different consumers
   can require different versions of the same ``python-require``. Being private, they cannot
   be overridden from downstream in any way.
-- ``python_requires`` cannot use regular ``requires`` or ``tool_requires``.
+- ``python_requires`` cannot use regular ``requires`` or ``tool_requires`` themselves. Having a ``requirements()`` (and similar)
+  methods to be inherited by recipes is possible and allowed, but the ``python_requires`` class itself cannot use them.
 - ``python_requires`` cannot be "aliased".
 - ``python_requires`` can use native python ``import`` to other python files, as long as these are
   exported together with the recipe.

diff --git a/2/conan.pdf b/2/conan.pdf
diff --git a/2/reference/extensions/python_requires.html b/2/reference/extensions/python_requires.html
@@ -387,7 +387,8 @@ <h2>Resolution of python_requires<a class="headerlink" href="#resolution-of-pyth
 <li><p>Python requires are private to the consumers. They are not transitive. Different consumers
 can require different versions of the same <code class="docutils literal notranslate"><span class="pre">python-require</span></code>. Being private, they cannot
 be overridden from downstream in any way.</p></li>
-<li><p><code class="docutils literal notranslate"><span class="pre">python_requires</span></code> cannot use regular <code class="docutils literal notranslate"><span class="pre">requires</span></code> or <code class="docutils literal notranslate"><span class="pre">tool_requires</span></code>.</p></li>
+<li><p><code class="docutils literal notranslate"><span class="pre">python_requires</span></code> cannot use regular <code class="docutils literal notranslate"><span class="pre">requires</span></code> or <code class="docutils literal notranslate"><span class="pre">tool_requires</span></code> themselves. Having a <code class="docutils literal notranslate"><span class="pre">requirements()</span></code> (and similar)
+methods to be inherited by recipes is possible and allowed, but the <code class="docutils literal notranslate"><span class="pre">python_requires</span></code> class itself cannot use them.</p></li>
 <li><p><code class="docutils literal notranslate"><span class="pre">python_requires</span></code> cannot be “aliased”.</p></li>
 <li><p><code class="docutils literal notranslate"><span class="pre">python_requires</span></code> can use native python <code class="docutils literal notranslate"><span class="pre">import</span></code> to other python files, as long as these are
 exported together with the recipe.</p></li>

diff --git a/2/searchindex.js b/2/searchindex.js