# PYNQ Composable c\_dict issue

**URL:** <https://discuss.pynq.io/t/pynq-composable-c-dict-issue/4240>\
**Category:** Support\
**Created:** [May 24, 2022, 4:20pm UTC](https://discuss.pynq.io/t/pynq-composable-c-dict-issue/4240 "2022-05-24T16:20:06Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![marioruiz](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/marioruiz/32/2177_2.png) [@marioruiz](https://discuss.pynq.io/u/marioruiz)\
**Post date:** [May 24, 2022, 4:25pm UTC](https://discuss.pynq.io/t/pynq-composable-c-dict-issue/4240/2 "2022-05-24T16:25:32Z")

</div>

@briansune

This has been documented on other posts. Since pynq 2.7, the pynq package is installed in a virtual environment. Running as sudo sources the environment whereas the regular user is not sourcing the venv.

> [@No Module called "pynq"](https://discuss.pynq.io/t/no-module-called-pynq/3513/2):
>
> Hi there, What exactly are you running to cause the “the target device has no module called “Pynq””? And are you running that from inside the pynq virtualenv? Could you try running these commands as root, first sourcing the virtualenv with source /etc/profile.d/pynq\_venv.sh Thanks Shawn

Mario

---

_[View the full topic](https://discuss.pynq.io/t/pynq-composable-c-dict-issue/4240)._