> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/core/get-started/faq/python-undefined-symbol-unicode.md).

# "undefined symbol: PyUnicodeUCS4\_..." or "undefined symbol: PyUnicodeUCS2\_..." errors

World's #1 PDF SDK Library for Web, Mobile, Server, Desktop

This error means there is a mismatch between the byte size of Unicode characters used by the environment used to build the wrappers and the environment used to run them. [Read this](https://docs.python.org/2/faq/extending.html#when-importing-module-x-why-do-i-get-undefined-symbol-pyunicodeucs2) for more information.

If this error occured when using python environments with [pyenv](https://github.com/pyenv/pyenv/), you can simply reinstall the python version used to run the tests with the required Unicode character size. For example, if your Python version was `2.7.16` and you received the `undefined symbol: PyUnicodeUCS2_` error when running the samples, execute:

{% tabs %}
{% tab title="Shell" %}
{% code lineNumbers="true" %}

```sh
pyenv uninstall 2.7.16
```

{% endcode %}
{% endtab %}
{% endtabs %}

followed by

{% tabs %}
{% tab title="Shell" %}
{% code lineNumbers="true" %}

```sh
PYTHON_CONFIGURE_OPTS="--enable-unicode=ucs2" pyenv install 2.7.16
```

{% endcode %}
{% endtab %}
{% endtabs %}

then set your [pyenv](https://github.com/pyenv/pyenv/) environment to `2.7.16` and rerun the samples.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.apryse.com/core/get-started/faq/python-undefined-symbol-unicode.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.