This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/beam.git
The following commit(s) were added to refs/heads/asf-site by this push:
new a6559575051 Publishing website 2026/02/10 23:51:42 at commit 195cc59
a6559575051 is described below
commit a6559575051322507abef7aac6181bda826683bc
Author: runner <runner@main-runner-vplcm-jr7hd>
AuthorDate: Tue Feb 10 23:51:42 2026 +0000
Publishing website 2026/02/10 23:51:42 at commit 195cc59
---
.../sdks/python-pipeline-dependencies/index.html | 12 +++++++++++-
website/generated-content/sitemap.xml | 2 +-
2 files changed, 12 insertions(+), 2 deletions(-)
diff --git
a/website/generated-content/documentation/sdks/python-pipeline-dependencies/index.html
b/website/generated-content/documentation/sdks/python-pipeline-dependencies/index.html
index e6865502f6a..6747fb2e856 100644
---
a/website/generated-content/documentation/sdks/python-pipeline-dependencies/index.html
+++
b/website/generated-content/documentation/sdks/python-pipeline-dependencies/index.html
@@ -76,7 +76,17 @@ RUN python -m pip install -r /tmp/requirements.txt
</code></pre></li></ol><p><strong>Note:</strong> It is not necessary to supply
the <code>--requirements_file</code> <a href=#pypi-dependencies>option</a> if
the dependencies of your package are defined in the
<code>install_requires</code> field of the <code>setup.py</code> file (see step
1).
However unlike with the <code>--requirements_file</code> option, when you use
the <code>--setup_file</code> option, Beam doesn’t stage the dependent
packages to the runner.
Only the pipeline package is staged. If they aren’t already provided in
the runtime environment,
-the package dependencies are installed from PyPI at runtime.</p><h2
id=nonpython>Non-Python Dependencies or PyPI Dependencies with Non-Python
Dependencies</h2><p>If your pipeline uses non-Python packages, such as packages
that require installation using the <code>apt install</code> command, or uses a
PyPI package that depends on non-Python dependencies during package
installation, we recommend installing them using a <a
href=#custom-containers>custom container</a>.
+the package dependencies are installed from PyPI at
runtime.</p><p><strong>Note:</strong> When using the install_requires argument,
ensure that the listed packages are compatible with the version of setuptools
used by the runner’s environment.
+If your dependencies require a backward-compatible version of setuptools to
build successfully, you can force a specific version requirement using the
setup_requires argument.</p><p>For instance, to ensure compatibility with
packages that still rely on (now deprecated) <code>pkg_resources</code>
module:</p><pre><code> import setuptools
+
+ setuptools.setup(
+ name='PACKAGE-NAME',
+ version='PACKAGE-VERSION',
+ setup_requires=['setuptools<82.0.0'],
+ install_requires=['incompatible-package', ...],
+ packages=setuptools.find_packages()
+ )
+</code></pre><h2 id=nonpython>Non-Python Dependencies or PyPI Dependencies
with Non-Python Dependencies</h2><p>If your pipeline uses non-Python packages,
such as packages that require installation using the <code>apt install</code>
command, or uses a PyPI package that depends on non-Python dependencies during
package installation, we recommend installing them using a <a
href=#custom-containers>custom container</a>.
Otherwise, you must perform the following steps.</p><ol><li><p><a
href=#multiple-file-dependencies>Structure your pipeline as a
package</a>.</p></li><li><p>Add the required installation commands for the
non-Python dependencies, such as the <code>apt install</code> commands, to the
list of <code>CUSTOM_COMMANDS</code> in your <code>setup.py</code> file. See
the <a
href=https://github.com/apache/beam/blob/master/sdks/python/apache_beam/examples/complete/juliaset/setup.py>Juliaset
setup.py [...]
</code></pre></li></ol><p><strong>Note:</strong> Because custom commands
execute after the dependencies for your workflow are installed (by
<code>pip</code>), you should omit the PyPI package dependency from the
pipeline’s <code>requirements.txt</code> file and from the
<code>install_requires</code> parameter in the <code>setuptools.setup()</code>
call of your <code>setup.py</code> file.</p><h2
id=pre-building-sdk-container-image>Pre-building SDK Container Image</h2><p>In
pipeline [...]
However, it may be possible to pre-build the SDK containers and perform the
dependency installation once before the workers start with
<code>--prebuild_sdk_container_engine</code>. For instructions of how to use
pre-building with Google Cloud
diff --git a/website/generated-content/sitemap.xml
b/website/generated-content/sitemap.xml
index cba4f288191..88b7eecefab 100644
--- a/website/generated-content/sitemap.xml
+++ b/website/generated-content/sitemap.xml
@@ -1 +1 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?><urlset
xmlns="http://www.sitemaps.org/schemas/sitemap/0.9";
xmlns:xhtml="http://www.w3.org/1999/xhtml";><url><loc>/blog/beam-2.71.0/</loc><lastmod>2026-02-10T11:18:26-05:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2026-02-10T11:18:26-05:00</lastmod></url><url><loc>/blog/</loc><lastmod>2026-02-10T11:18:26-05:00</lastmod></url><url><loc>/categories/</loc><lastmod>2026-02-10T11:18:26-05:00</lastmod></url><url><loc>/catego
[...]
\ No newline at end of file
+<?xml version="1.0" encoding="utf-8" standalone="yes"?><urlset
xmlns="http://www.sitemaps.org/schemas/sitemap/0.9";
xmlns:xhtml="http://www.w3.org/1999/xhtml";><url><loc>/blog/beam-2.71.0/</loc><lastmod>2026-02-10T18:13:37-05:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2026-02-10T18:13:37-05:00</lastmod></url><url><loc>/blog/</loc><lastmod>2026-02-10T18:13:37-05:00</lastmod></url><url><loc>/categories/</loc><lastmod>2026-02-10T18:13:37-05:00</lastmod></url><url><loc>/catego
[...]
\ No newline at end of file
