Merge branch 'main' into test-sis

Former-commit-id: 0a0ceae

Author: sfc-gh-dmatthews

components/blocks/callout.module.css

@@ -7,10 +7,6 @@
   @apply text-gray-90 !important;
 }
 
-.Container p > code {
-  @apply border border-gray-40 text-red-70 rounded-md px-1 mx-1 break-words;
-}
-
 .Container p:only-child,
 .Container p:last-child,
 .Container section:last-child,

components/layouts/flex.js

@@ -1,8 +1,15 @@
 import styles from "./flex.module.css";
+import classNames from "classnames";
 
 // Simple horizontal flex container used for MDX.
-const Flex = ({ children }) => {
-  return <section className={styles.Container}>{children}</section>;
+const Flex = ({ wrap = false, children }) => {
+  return (
+    <section
+      className={classNames(styles.Container, wrap ? styles.wrapContainer : "")}
+    >
+      {children}
+    </section>
+  );
 };
 
 export default Flex;

components/layouts/flex.module.css

@@ -1,3 +1,11 @@
 .Container {
-  @apply flex flex-col lg:flex-row;
+  @apply flex flex-col lg:flex-row text-gray-90;
+}
+
+:global(.dark) .Container {
+  @apply text-gray-40;
+}
+
+.wrapContainer {
+  @apply flex-wrap flex-row;
 }

content/deploy/community-cloud/deploy-your-app/app-dependencies.md

@@ -23,7 +23,13 @@ directory as your app's entrypoint file.
 
 With each `import` statement in your script, you are bringing in a Python dependency. You need to tell Community Cloud how to install those dependencies through a Python package manager. We recommend using a `requirements.txt` file, which is based on `pip`.
 
-You should _not_ include <a href="https://docs.python.org/3/py-modindex.html" target="_blank">built-in Python libraries</a> like `math` or `random` in your `requirements.txt` file. These are a part of Python and aren't installed separately. Also, Community Cloud has `streamlit` installed by default. You don't strictly need to include `streamlit` unless you want to pin or restrict the version. If you deploy an app without a `requirements.txt` file, your app will run in an environment with just `streamlit` (and its dependencies) installed.
+You should _not_ include <a href="https://docs.python.org/3/py-modindex.html" target="_blank">built-in Python libraries</a> like `math`, `random`, or `distutils` in your `requirements.txt` file. These are a part of Python and aren't installed separately. Also, Community Cloud has `streamlit` installed by default. You don't strictly need to include `streamlit` unless you want to pin or restrict the version. If you deploy an app without a `requirements.txt` file, your app will run in an environment with just `streamlit` (and its dependencies) installed.
+
+<Important>
+
+The version of Python you use is important! Built-in libraries change between versions of Python and other libraries may have specific version requirements, too. Whenever Streamlit supports a new version of Python, Community Cloud quickly follows to default to that new version of Python. Always develop your app in the same version of Python you will use to deploy it. For more information about setting the version of Python when you deploy your app, see [Optional: Configure secrets and Python version](/deploy/streamlit-community-cloud/deploy-your-app/deploy#optional-configure-secrets-and-python-version).
+
+</Important>
 
 If you have a script like the following, no extra dependencies would be needed since `pandas` and `numpy` are installed as direct dependencies of `streamlit`. Similarly, `math` and `random` are built into Python.
 
@@ -100,7 +106,7 @@ You should only use one dependency file for your app. If you include more than o
 
 ## apt-get dependencies
 
-For many apps, a `packages.txt` file is not required. However, if your script requires any software to be installed that is not a Python package, you need a `packages.txt` file. Community Cloud is built on Debian Linux. Anything you want to `apt-get install` must go in your `packages.txt` file.
+For many apps, a `packages.txt` file is not required. However, if your script requires any software to be installed that is not a Python package, you need a `packages.txt` file. Community Cloud is built on Debian Linux. Anything you want to `apt-get install` must go in your `packages.txt` file. To browse available packages that can be installed, see the Debian 11 ("bullseye") [package list](https://packages.debian.org/bullseye/).
 
 If `packages.txt` exists in the root directory of your repository we automatically detect it, parse it, and install the listed packages. You can read more about apt-get in <a href="https://linux.die.net/man/8/apt-get" target="_blank">Linux documentation</a>.
 

content/deploy/community-cloud/status-and-limitations.md

@@ -26,6 +26,13 @@ You can deploy multiple apps from your repository, and your entrypoint file(s) m
 - Community Cloud only recognizes one `.streamlit/configuration.toml` file at the root (of each branch) of your repository.
 - You must declare image, video, and audio file paths for Streamlit commands relative to the root of your repository. For example, `st.image`, `st.logo`, and the `page_icon` parameter in `st.set_page_config` expect file locations relative to your working directory (i.e. where you execute `streamlit run`).
 
+## Linux environments
+
+Community Cloud is built on Debian Linux.
+
+- Community Cloud uses Debian 11 ("bullseye"). To browse available packages that can be installed, see the [package list](https://packages.debian.org/bullseye/).
+- All file paths must use forward-slash path separators.
+
 ## Python environments
 
 - You cannot mix and match Python package managers for a single app. Community Cloud configures your app's Python environment based on the first environment configuration file it finds. For more information, see [Other Python package managers](/deploy/streamlit-community-cloud/deploy-your-app/app-dependencies#other-python-package-managers).
@@ -62,7 +69,7 @@ If you need to whitelist IP addresses for a connection, Community Cloud is curre
 
 </Warning>
 
-<div style={{ display: "flex", flexWrap: "wrap", flexDirection: "row", alignItems: "start" }}>
+<Flex wrap >
     <div style={{ width: "150px" }}>35.230.127.150</div>
     <div style={{ width: "150px" }}>35.203.151.101</div>
     <div style={{ width: "150px" }}>34.19.100.134</div>
@@ -81,11 +88,10 @@ If you need to whitelist IP addresses for a connection, Community Cloud is curre
     <div style={{ width: "150px" }}>35.227.190.87</div>
     <div style={{ width: "150px" }}>35.199.156.97</div>
     <div style={{ width: "150px" }}>34.82.135.155</div>
-</div>
+</Flex>
 
 ## Other limitations
 
 - When you print something to the Cloud logs, you may need to do a `sys.stdout.flush()` before it shows up.
 - Community Cloud hosts all apps in the United States. This is currently not configurable.
-- Community Cloud is built on Debian Linux. All file paths must use forward-slash path separators.
 - Community Cloud rate limits app updates from GitHub to no more than five per minute.

content/deploy/concepts/dependencies.md

@@ -22,7 +22,13 @@ If you are using Streamlit Community Cloud, you'll have the latest version of St
 
 ### `pip` and `requirements.txt`
 
-Since `pip` comes by default with Python, the most common way to configure your Python environment is with a `requirements.txt` file. Each line of a `requirements.txt` file is a package to `pip install`. You should _not_ include <a href="https://docs.python.org/3/py-modindex.html" target="_blank">built-in Python libraries</a> like `math` or `random` in your `requirements.txt` file. These are a part of Python and aren't installed separately.
+Since `pip` comes by default with Python, the most common way to configure your Python environment is with a `requirements.txt` file. Each line of a `requirements.txt` file is a package to `pip install`. You should _not_ include <a href="https://docs.python.org/3/py-modindex.html" target="_blank">built-in Python libraries</a> like `math`, `random`, or `distutils` in your `requirements.txt` file. These are a part of Python and aren't installed separately.
+
+<Tip>
+
+Since dependencies may rely on a specific version of Python, always be aware of the Python version used in your development environment, and select the same version for your deployment environment.
+
+</Tip>
 
 If you have a script like the following, you would only need to install Streamlit. No extra dependencies would be needed since `pandas` and `numpy` are installed as direct dependencies of `streamlit`. Similarly, `math` and `random` are built into Python.
 

content/deploy/snowflake/_index.md

@@ -18,7 +18,7 @@ Host your apps alongside your data in a single, global platform. Snowflake provi
     <Tile
         icon="code"
         title="Examples"
-        text="Explore a plethora of example apps in Snowflake Labs' snowflake-demo-streamlit repository."
+        text="Explore a wide variety of example apps in Snowflake Labs' snowflake-demo-streamlit repository."
         link="https://github.com/Snowflake-Labs/snowflake-demo-streamlit"
         background="lightBlue-70"
     />
@@ -31,27 +31,27 @@ Host your apps alongside your data in a single, global platform. Snowflake provi
     />
 </TileContainer>
 
-There are three ways to host Streamlit apps in Snowflake.
+There are three ways to host Streamlit apps in Snowflake:
 
 <InlineCalloutContainer>
     <InlineCallout
         color="lightBlue-70"
         icon="bolt"
         bold="Streamlit in Snowflake."
         href="https://docs.snowflake.com/developer-guide/streamlit/about-streamlit"
-    >Run your Streamlit app as a native object in Snowflake. Enjoy an in-browser editor and minimal work to configure your environment. Share your app with other users in your Snowflake account through role-based access control. This is a great way to deploy apps internally for your business. Check out Snowflake docs!</InlineCallout>
+    >Run your Streamlit app as a native object in Snowflake. Enjoy an in-browser editor and minimal work to configure your environment. Share your app with other users in your Snowflake account through role-based access control (RBAC). This is a great way to deploy apps internally for your business. Check out Snowflake docs!</InlineCallout>
     <InlineCallout
         color="lightBlue-70"
         icon="ac_unit"
         bold="Snowflake Native Apps."
         href="https://docs.snowflake.com/en/developer-guide/native-apps/adding-streamlit"
-    >Package your app with data and share it with other Snowflake accounts. This is a great way to share apps and their underlying data with other organizations who use Snowflake so they can run it in their own account. Check out Snowflake docs!</InlineCallout>
+    >Package your app with data and share it with other Snowflake accounts. This is a great way to share apps and their underlying data with other organizations who use Snowflake. Check out Snowflake docs!</InlineCallout>
     <InlineCallout
         color="lightBlue-70"
         icon="web_asset"
         bold="Snowpark Container Services."
         href="https://docs.snowflake.com/en/developer-guide/snowpark-container-services/overview"
-    >Deploy your app in a container that's optimized to run in Snowflake. This is the most flexible option where you can use any library. Share your app publicly or privately. Check out Snowflake docs!</InlineCallout>
+    >Deploy your app in a container that's optimized to run in Snowflake. This is the most flexible option, where you can use any library and assign a public URL to your app. Manage your allowed viewers through your Snowflake account. Check out Snowflake docs!</InlineCallout>
 </InlineCalloutContainer>
 
 <Note>

content/deploy/tutorials/kubernetes.md

@@ -88,7 +88,7 @@ Docker builds images by reading the instructions from a `Dockerfile`. A `Docke
 Here's an example `Dockerfile` that you can add to the root of your directory.
 
 ```docker
-FROM python:3.8-slim
+FROM python:3.9-slim
 
 RUN groupadd --gid 1000 appuser \
     && useradd --uid 1000 --gid 1000 -ms /bin/bash appuser

content/develop/api-reference/configuration/config-toml.md

@@ -21,7 +21,7 @@ To define your configuration globally, you must first locate your global `.strea
 
 ```toml
 [client]
-showErrorDetails = false
+showErrorDetails = "none"
 
 [theme]
 primaryColor = "#F63366"
@@ -69,7 +69,7 @@ level = "info"
 # Python's documentation for available attributes:
 # https://docs.python.org/3/library/logging.html#formatter-objects
 # Default: "%(asctime)s %(message)s"
-messageFormat = "%(asctime)s %(levelname) -7s %(name)s: %(message)s"
+messageFormat = "%(asctime)s %(message)s"
 ```
 
 #### Client
@@ -78,26 +78,39 @@ messageFormat = "%(asctime)s %(levelname) -7s %(name)s: %(message)s"
 [client]
 
 # Controls whether uncaught app exceptions and deprecation warnings
-# are displayed in the browser. By default, this is set to True and
-# Streamlit displays app exceptions and associated tracebacks, and
-# deprecation warnings, in the browser.
-# If set to False, deprecation warnings and full exception messages
-# will print to the console only. Exceptions will still display in the
-# browser with a generic error message. For now, the exception type and
-# traceback show in the browser also, but they will be removed in the
-# future.
-# Default: true
-showErrorDetails = true
+# are displayed in the browser. This can be one of the following:
+# - "full"       : In the browser, Streamlit displays app deprecation
+#                  warnings and exceptions, including exception types,
+#                  exception messages, and associated tracebacks.
+# - "stacktrace" : In the browser, Streamlit displays exceptions,
+#                  including exception types, generic exception messages,
+#                  and associated tracebacks. Deprecation warnings and
+#                  full exception messages will only print to the
+#                  console.
+# - "type"       : In the browser, Streamlit displays exception types and
+#                  generic exception messages. Deprecation warnings, full
+#                  exception messages, and associated tracebacks only
+#                  print to the console.
+# - "none"       : In the browser, Streamlit displays generic exception
+#                  messages. Deprecation warnings, full exception
+#                  messages, associated tracebacks, and exception types
+#                  will only print to the console.
+# - True         : This is deprecated. Streamlit displays "full"
+#                  error details.
+# - False        : This is deprecated. Streamlit displays "stacktrace"
+#                  error details.
+# Default: "full"
+showErrorDetails = "full"
 
 # Change the visibility of items in the toolbar, options menu,
 # and settings dialog (top right of the app).
 # Allowed values:
-# * "auto"      : Show the developer options if the app is accessed through
+# - "auto"      : Show the developer options if the app is accessed through
 #                 localhost or through Streamlit Community Cloud as a developer.
 #                 Hide them otherwise.
-# * "developer" : Show the developer options.
-# * "viewer"    : Hide the developer options.
-# * "minimal"   : Show only options set externally (e.g. through
+# - "developer" : Show the developer options.
+# - "viewer"    : Hide the developer options.
+# - "minimal"   : Show only options set externally (e.g. through
 #                 Streamlit Community Cloud) or through st.set_page_config.
 #                 If there are no options left, hide the menu.
 # Default: "auto"
@@ -140,9 +153,9 @@ enforceSerializableSessionState = false
 # during a script re-run. For more information, check out the docs:
 # https://docs.streamlit.io/develop/concepts/design/custom-classes#enums
 # Allowed values:
-# * "off"          : Disables Enum coercion.
-# * "nameOnly"     : Enum classes can be coerced if their member names match.
-# * "nameAndValue" : Enum classes can be coerced if their member names AND
+# - "off"          : Disables Enum coercion.
+# - "nameOnly"     : Enum classes can be coerced if their member names match.
+# - "nameAndValue" : Enum classes can be coerced if their member names AND
 #                    member values match.
 # Default: "nameOnly"
 enumCoercion = "nameOnly"
@@ -162,11 +175,11 @@ folderWatchBlacklist = []
 # Change the type of file watcher used by Streamlit, or turn it off
 # completely.
 # Allowed values:
-# * "auto"     : Streamlit will attempt to use the watchdog module, and
+# - "auto"     : Streamlit will attempt to use the watchdog module, and
 #                falls back to polling if watchdog is not available.
-# * "watchdog" : Force Streamlit to use the watchdog module.
-# * "poll"     : Force Streamlit to always use polling.
-# * "none"     : Streamlit will not watch files.
+# - "watchdog" : Force Streamlit to use the watchdog module.
+# - "poll"     : Force Streamlit to always use polling.
+# - "none"     : Streamlit will not watch files.
 # Default: "auto"
 fileWatcherType = "auto"
 
@@ -201,19 +214,17 @@ port = 8501
 # Default: ""
 baseUrlPath = ""
 
-# Enables support for Cross-Origin Resource Sharing (CORS) protection, for
-# added security.
-# Due to conflicts between CORS and XSRF, if `server.enableXsrfProtection` is
-# on and `server.enableCORS` is off at the same time, we will prioritize
-# `server.enableXsrfProtection`.
+# Enables support for Cross-Origin Resource Sharing (CORS) protection,
+# for added security.
+# If XSRF protection is enabled and CORS protection is disabled at the
+# same time, Streamlit will enable them both instead.
 # Default: true
 enableCORS = true
 
 # Enables support for Cross-Site Request Forgery (XSRF) protection, for
 # added security.
-# Due to conflicts between CORS and XSRF, if `server.enableXsrfProtection` is
-# on and `server.enableCORS` is off at the same time, we will prioritize
-# `server.enableXsrfProtection`.
+# If XSRF protection is enabled and CORS protection is disabled at the
+# same time, Streamlit will enable them both instead.
 # Default: true
 enableXsrfProtection = true
 

content/develop/concepts/app-design/button-behavior-and-examples.md

@@ -365,10 +365,8 @@ if 'processed' not in st.session_state:
 if st.button('Process'):
     result = expensive_process(option, add)
     st.session_state.processed[option] = result
-
-if option in st.session_state.processed:
     st.write(f'Option {option} processed with add {add}')
-    st.write(st.session_state.processed[option][0])
+    result[0]
 ```
 
 Astute observers may think, "This feels a little like caching." We are only saving results relative to one parameter, but the pattern could easily be expanded to save results relative to both parameters. In that sense, yes, it has some similarities to caching, but also some important differences. When you save results in `st.session_state`, the results are only available to the current user in their current session. If you use [`st.cache_data`](/develop/api-reference/caching-and-state/st.cache_data) instead, the results are available to all users across all sessions. Furthermore, if you want to update a saved result, you have to clear all saved results for that function to do so.