This is an automated email from the ASF dual-hosted git repository.
github-actions[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 468e1792d7b Publishing website 2026/07/28 18:07:30 at commit fc0d989
468e1792d7b is described below
commit 468e1792d7bc4c3ff5540c54bb24e8bd41ff1391
Author: runner <runner@main-runner-2404-9kmqn-rcvfz>
AuthorDate: Tue Jul 28 18:07:31 2026 +0000
Publishing website 2026/07/28 18:07:30 at commit fc0d989
---
.../sdks/python-pipeline-dependencies/index.html | 11 +++++++++--
website/generated-content/sitemap.xml | 2 +-
2 files changed, 10 insertions(+), 3 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 b42dbb9300b..3da33ec1340 100644
---
a/website/generated-content/documentation/sdks/python-pipeline-dependencies/index.html
+++
b/website/generated-content/documentation/sdks/python-pipeline-dependencies/index.html
@@ -35,7 +35,7 @@
<img class=banner-img-mobile
src=/images/banners/tour-of-beam/tour-of-beam-mobile.png alt="Start Tour of
Beam"></a></div><div class=swiper-slide><a
href=https://beam.apache.org/documentation/ml/overview/><img
class=banner-img-desktop
src=/images/banners/machine-learning/machine-learning-desktop.jpg alt="Machine
Learning">
<img class=banner-img-mobile
src=/images/banners/machine-learning/machine-learning-mobile.jpg alt="Machine
Learning"></a></div></div><div class=swiper-pagination></div><div
class=swiper-button-prev></div><div
class=swiper-button-next></div></div><script
src=/js/swiper-bundle.min.min.e0e8f81b0b15728d35ff73c07f42ddbb17a108d6f23df4953cb3e60df7ade675.js></script>
<script
src=/js/sliders/top-banners.min.afa7d0a19acf7a3b28ca369490b3d401a619562a2a4c9612577be2f66a4b9855.js></script>
-<script>function showSearch(){addPlaceholder();var
e,t=document.querySelector(".searchBar");t.classList.remove("disappear"),e=document.querySelector("#iconsBar"),e.classList.add("disappear")}function
addPlaceholder(){$("input:text").attr("placeholder","What are you looking
for?")}function endSearch(){var
e,t=document.querySelector(".searchBar");t.classList.add("disappear"),e=document.querySelector("#iconsBar"),e.classList.remove("disappear")}function
blockScroll(){$("body").toggleClass(" [...]
+<script>function showSearch(){addPlaceholder();var
e,t=document.querySelector(".searchBar");t.classList.remove("disappear"),e=document.querySelector("#iconsBar"),e.classList.add("disappear")}function
addPlaceholder(){$("input:text").attr("placeholder","What are you looking
for?")}function endSearch(){var
e,t=document.querySelector(".searchBar");t.classList.add("disappear"),e=document.querySelector("#iconsBar"),e.classList.remove("disappear")}function
blockScroll(){$("body").toggleClass(" [...]
<code>requirements.txt</code> file. For more complex scenarios, define the <a
href=#multiple-file-dependencies>pipeline in a package</a> and consider
installing your dependencies in a <a href=#custom-containers>custom
container</a>.</p><p>To supply a requirements.txt file:</p><ol><li><p>Find out
which packages are installed on your machine. Run the following
command:</p><pre><code> pip freeze > requirements.txt
</code></pre><p>This command creates a <code>requirements.txt</code> file that
lists all packages that are installed on your machine, regardless of where they
were installed from.</p></li><li><p>Edit the <code>requirements.txt</code> file
and delete all packages that are not relevant to your code.</p></li><li><p>Run
your pipeline with the following command-line option:</p><pre><code>
--requirements_file requirements.txt
</code></pre><p>The runner will use the <code>requirements.txt</code> file to
install your additional dependencies onto the remote
workers.</p></li></ol><blockquote><p><strong>NOTE</strong>: As an alternative
to <code>pip freeze</code>, use a library like <a
href=https://github.com/jazzband/pip-tools>pip-tools</a> to compile all of the
dependencies required for the pipeline from a <code>requirements.in</code>
file. In the <code>requirements.in</code> file, only the top-level dependencies
[...]
@@ -53,7 +53,14 @@ RUN python -m pip install -r /tmp/requirements.txt
</code></pre><p>where package-name is the package’s tarball. You can
build the package tarball using a command line tool called <a
href=https://setuptools.pypa.io/en/latest/userguide/quickstart.html#install-build>build</a>.</p><pre><code>
# Install build using pip
pip install --upgrade build
python -m build --sdist
-</code></pre><p>See the <a
href=https://pypa-build.readthedocs.io/en/latest/index.html>build
documentation</a> for more details on this command.</p></li></ol></li></ol><h2
id=multiple-file-dependencies>Multiple File Dependencies</h2><p>Often, your
pipeline code spans multiple files. To run your project remotely, you must
group these files as a Python package and specify the package when you run your
pipeline. When the remote workers start, they will install your package. To
group your fi [...]
+</code></pre><p>See the <a
href=https://pypa-build.readthedocs.io/en/latest/index.html>build
documentation</a> for more details on this command.</p></li></ol></li></ol><h2
id=staging-files>Staging Individual Files</h2><p>If your pipeline relies on one
or more individual Python files or non-Python data files that do not need to be
packaged as a full Python package, you can stage them individually to the
remote workers.</p><p>To stage individual files, run your pipeline with the
<code>--fi [...]
+</code></pre><p>When the pipeline runs, the runner uploads these files and
makes them available on the workers in the worker’s staged files
directory.</p><h3 id=accessing-staged-files-on-the-workers>Accessing Staged
Files on the Workers</h3><p>Staged files are downloaded onto the
worker:</p><ul><li><p><strong>Python modules</strong>: Starting with Apache
Beam 2.76.0, to make it easy to import staged Python files as modules, Beam
automatically appends the worker’s staged files [...]
+</code></pre></li><li><p><strong>Data or configuration files</strong>: If you
staged non-Python files (such as a JSON config), they are downloaded to the
staged files directory. You can locate this directory on the worker by reading
the <code>SEMI_PERSISTENT_DIRECTORY</code> environment variable, or look for
<code>/tmp/staged</code> which is the default location for staged files on
containerized runners:</p><pre><code>import os
+staged_dir = os.environ.get('SEMI_PERSISTENT_DIRECTORY', '/tmp/staged')
+config_path = os.path.join(staged_dir, 'data_config.json')
+</code></pre></li></ul><h3 id=importing-plugins-on-worker-startup>Importing
Plugins on Worker Startup</h3><p>You can use staged files in combination with
the <code>--beam_plugins</code> pipeline option (supported starting with Apache
Beam 2.76.0) to run initialization code on the workers before any processing
starts.</p><p>To use a staged file as a plugin:</p><ol><li>Stage the plugin
file (e.g. <code>my_custom_plugin.py</code>) using
<code>--file_to_stage</code>.</li><li>Reference the mo [...]
+ --beam_plugins="my_custom_plugin"
+</code></pre><p>This instructs the SDK worker to import
<code>my_custom_plugin</code> immediately on startup, triggering any
initialization logic defined in the module.</p><h2
id=multiple-file-dependencies>Multiple File Dependencies</h2><p>Often, your
pipeline code spans multiple files. To run your project remotely, it is best to
group these files as a Python package and specify the package when you run your
pipeline. When the remote workers start, they will install your package. To
grou [...]
setuptools.setup(
name='PACKAGE-NAME',
diff --git a/website/generated-content/sitemap.xml
b/website/generated-content/sitemap.xml
index 1f2b235900a..829112b4c8b 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-summit-2026-interview-with-raj-katakam/</loc><lastmod>2026-07-28T07:38:57-04:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2026-07-28T07:38:57-04:00</lastmod></url><url><loc>/blog/</loc><lastmod>2026-07-28T07:38:57-04:00</lastmod></url><url><loc>/categories/</loc><lastmod>2026-07-28T07:38:57-04:00<
[...]
\ 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-summit-2026-interview-with-raj-katakam/</loc><lastmod>2026-07-28T13:28:10-04:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2026-07-28T13:28:10-04:00</lastmod></url><url><loc>/blog/</loc><lastmod>2026-07-28T13:28:10-04:00</lastmod></url><url><loc>/categories/</loc><lastmod>2026-07-28T13:28:10-04:00<
[...]
\ No newline at end of file
