From 124e6b6a9c92b5494ea919742863a0c4ec57f722 Mon Sep 17 00:00:00 2001
From: rosetn <40248483+rosetn@users.noreply.github.com>
Date: Wed, 7 Aug 2019 12:03:49 -0700
Subject: [PATCH] Update python-pipeline-dependencies.md

---
 website/src/documentation/sdks/python-pipeline-dependencies.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/src/documentation/sdks/python-pipeline-dependencies.md b/website/src/documentation/sdks/python-pipeline-dependencies.md
index 327e00bd07c0d..46d2fc40907bd 100644
--- a/website/src/documentation/sdks/python-pipeline-dependencies.md
+++ b/website/src/documentation/sdks/python-pipeline-dependencies.md
@@ -23,7 +23,7 @@ limitations under the License.
 
 When you run your pipeline locally, the packages that your pipeline depends on are available because they are installed on your local machine. However, when you want to run your pipeline remotely, you must make sure these dependencies are available on the remote machines. This tutorial shows you how to make your dependencies available to the remote workers. Each section below refers to a different source that your package may have been installed from.
 
-**Note:** Remote workers used for pipeline execution typically have a standard Python 2.7 distribution installation. If your code relies only on standard Python packages, then you probably don't need to do anything on this page.
+**Note:** Remote workers used for pipeline execution typically have a standard Python distribution installation in a Debian-based container image. If your code relies only on standard Python packages, then you probably don't need to do anything on this page.
 
 
 ## PyPI Dependencies {#pypi-dependencies}