# venv error in Python when building or running application
## The library version does not match the environment version:

The problem is that pip (if you are using Python) finds the wrong versions of the library. 

For example: wavelink, if you leave the Python version as default (3.8), then due to the fact that wavelink requires Python >= 3.10, there will be completely different versions. 
And you can only find out about this by studying it at pypi.org.

### Solution:

You can change the Python version in the configuration file, or the dependency versions in the requirements.txt file.

```{eval-rst}
.. admonition:: Clue
   :class: hint

   If you can’t figure it out, write to support support@amverum.com. Please immediately indicate your user and project name. We will try to help.
```

## Not all files were deleted after the project was frozen:
If you freeze the project and immediately rebuild it, the venv folder in Artifacts, which is responsible for the Python environment, becomes damaged, 
not having time to delete before the new build, which causes errors like:
- ```ERROR: Could not install packages due to an OSError: [Errno 13] Permission denied: '/.local'```
- ```/app/venv/bin/python3: No module named pip.__main__; 'pip' is a package and cannot be directly executed```
- ```Error: [Errno 13] Permission denied: '/app/venv'```

You can solve it by completely clearing Artifacts. To do this, you need to go to "Settings" and freeze the project again, but for this 
give more time (about 20 seconds) so that the venv folder has time to be deleted and does not cause conflicts during the build.