# Latest released version (v7.9.1) python environment fails

**URL:** <https://discuss.elastic.co/t/latest-released-version-v7-9-1-python-environment-fails/249568>\
**Category:** Beats\
**Tags:** libbeat\
**Created:** [September 22, 2020, 5:40pm UTC](https://discuss.elastic.co/t/latest-released-version-v7-9-1-python-environment-fails/249568 "2020-09-22T17:40:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sean\_Houghton](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sean_houghton/32/29837_2.png) [@Sean\_Houghton](https://discuss.elastic.co/u/Sean_Houghton)\
**Post date:** [September 22, 2020, 5:40pm UTC](https://discuss.elastic.co/t/latest-released-version-v7-9-1-python-environment-fails/249568/1 "2020-09-22T17:40:55Z")

</div>

When using the latest pinned version (as everyone should be doing in production) the `python-dev` makefile target fails with setuptools errors

```auto
    ImportError: cannot import name 'Feature' from 'setuptools' (/private/tmp/foo/lib/python3.8/site-packages/setuptools/ __init__.py)

```

You can recreate this problem by cloning the repo, checking out v7.9.1 and running

```auto
python -m venv myenv
myenv/bin/pip install -r /path/to/beat/libbeat/tests/system/requirements.txt

```

It appears that this has been fixed on the `master` branch but the entire python environment seems to have been updated so it's hard to pinpoint exactly which change will fix this as a patch.

The build environment for beats is really, really complicated. Why are there not CI tests for the current release? Is v7.9.1 the current release?

---

<div class="post-metadata">

**Author:** ![Sean\_Houghton](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sean_houghton/32/29837_2.png) [@Sean\_Houghton](https://discuss.elastic.co/u/Sean_Houghton)\
**Post date:** [September 22, 2020, 6:00pm UTC](https://discuss.elastic.co/t/latest-released-version-v7-9-1-python-environment-fails/249568/2 "2020-09-22T18:00:47Z")

</div>

If anyone else needs to get past this problem you can hand-edit `libbeat/tests/system/requirements.txt` in your modcache and update Markupsafe to 1.1.1

Here's the relevant issue: [https://github.com/pallets/markupsafe/issues/116](https://github.com/pallets/markupsafe/issues/116)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [October 20, 2020, 8:00pm UTC](https://discuss.elastic.co/t/latest-released-version-v7-9-1-python-environment-fails/249568/3 "2020-10-20T20:00:52Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.