From 9e6400b7d1f9d525b7f45e7b56874dc830c02d1f Mon Sep 17 00:00:00 2001
From: Ashwin Srinath <3190405+shwina@users.noreply.github.com>
Date: Thu, 11 Jan 2024 18:38:07 -0600
Subject: [PATCH] Describe unpickling expectations when cudf.pandas is enabled
 (#14693)

Adds to the docs the unpickling expectations that were noted in #14692.

Authors:
  - Ashwin Srinath (https://github.com/shwina)

Approvers:
  - Matthew Roeschke (https://github.com/mroeschke)

URL: https://github.com/rapidsai/cudf/pull/14693
---
 docs/cudf/source/cudf_pandas/faq.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/docs/cudf/source/cudf_pandas/faq.md b/docs/cudf/source/cudf_pandas/faq.md
index bf9c2b98c2d..bbeaf0a5f00 100644
--- a/docs/cudf/source/cudf_pandas/faq.md
+++ b/docs/cudf/source/cudf_pandas/faq.md
@@ -113,6 +113,9 @@ There are a few known limitations that you should be aware of:
   pandas
 - `cudf.pandas` isn't compatible with directly using `import cudf`
    and is intended to be used with pandas-based workflows.
+- Unpickling objects that were pickled with "regular" pandas will not
+  work: you must have pickled an object with `cudf.pandas` enabled for
+  it to be unpickled when `cudf.pandas` is enabled.
 - Global variables can be accessed but can't be modified during CPU-fallback
 
   ```python