venvs | venvs creates virtualenvs | Build Tool library

I'm attempting to write a test fixture based on randomly generated data. This randomly generated data needs to be able to accept a seed so that we can generate the same data on two different computers at the same time.

I'm using the pytest parse.addoption fixture (I think it's a fixture) to add this ability.

My core issue is that I'd like to be able to parameterize a randomly generated list that uses a fixture as an argument.

VSCode wouldn't show venvs created with poetry in "change kernel" window.

I tried this thread but it didn't work. As well as the topic being 2 years old.
Eventhough I would like to avoid installing all the dependencies in local folder for each project (one of the suggested answers), I still tried it but VSCode doesn't see it either (.venv folder created inside the project).

Right now poetry saves all the venvs in: ~/.cache/pypoetry/virtualenvs after poetry shell any of the venvs. I added it to settings.json with

I see this issue posted alot...but no solutions thus far have worked for me (sorry about the repost).

PROBLEM I'm trying to run flask on my windows10 machine, and am unable to load a simple hello.py without a 404 error.

DEBUGGER The debugger is working for syntax errors (I can see the lines from hello.py file in my browser if I break the syntax in the file...but I'm getting no help on the 404 if the py file doesn't contain errors. The terminal also detects changes to the file it's supposed to load on the screen.

(I take it this means that the venv is set up properly, and the issue lies in the network handlers on windows..)

Things I've done I've tried.

1. Disabling all the firewalls
2. Restarting the machine (countless times)
3. netstat -aon to confirm my ports are being used by another service.
4. Uninstalling and reinstalling python
5. Setting up new venvs on different drives on my machine
6. allowing all permissions in windows for all users and guests prior to creating the virtual environment.
7. installing xampp and setting up ports for apache => flask run --port:PORT
8. Uninstalling xampp
9. sitting and crying in the corner of the shower with water running on my face

Code for hello.py

'''

I have created a package feed in Azure DevOps. Everything was working until pip version 22.0 was released.

Now when I try to install package from this feed using pip==22.0

Macbook Pro : Monterey

Intel Core i7

Brownie v1.17.2

Ganache CLI v6.12.2 (ganache-core: 2.13.2)

I am learning solidity according to reference(https://www.youtube.com/watch?v=M576WGiDBdQ&t=25510s).

I wrote and deployed a smart contract（scripts/deploy.py） using brownie framework, it worked.

Then tried to write a test script（tests/test_simple_storage.py） that gave me error information in the terminal.

Googled this and tried to delete all the files in brownie projects' build folder and deployed the contract（scripts/deploy.py） again， it's the same error.

And tried to change the private key and index, for accounts[0]to account[-1]and account[1]， the same error result.

FYI:I typed the command "ganache-cli —deterministic " in the terminal. So the account and private key are not random.

Saved the Ganache's account[0]'s private key in .env files,like this

.env

I am trying to install eth-brownie using the documentation, on Ubuntu 20.04.2. I've been going in circles for hours, trying to do everything the messages are telling me.

1. pipx install eth-brownie

   gives: Not installing to existing directory '/home/me/.local/pipx/venvs/eth-brownie'. Pass '--force' to force installation

2. fine, I tried with --force, and then got the following:

   Installing to existing directory '/home/me/.local/pipx/venvs/eth-brownie' The virtual environment was not created successfully because ensurepip is not available. On Debian/Ubuntu systems, you need to install the python3-venv package using the following command.

   apt-get install python3-venv

3. I know I already have python3, because when I type python3 I get: Python 3.8.5, blabla

   But ok, let's try doing what it says. Tried, asked to use sudo. Added 'sudo' in the beginning, and got: The following packages have unmet dependencies: python3-venv : Depends: python3.8-venv (>= 3.8.2-1~) but it is not going to be installed E: Unable to correct problems, you have held broken packages.

I searched for similar questions and have been going at it for hours. I tried the 'update' command, 'the 'upgrade' command, the 'dpkg' thing, and every suggestion I could find. I just want to have eth-brownie. Can someone please help?

I have different venvs in my machine in which I have python 3.10.

Now for a specific project, I realised that python 3.10 is not suitable as some libraries are still not compatible. Therefore when creating a new venv for a new project, I would like to downgrade python, say to 3.8, only for this specific venv.

How can I do that? What should I type onto the terminal to do this?

PS: I use VS and its terminal to create venv

on my windows system I've succesfully installed a virtual environment (python version is 3.9) using windows command prompt

python -m venv C:\my_path\my_venv

Always using windows command prompt, I'm able to activate the created venv via

C:\my_path\my_venv\Scripts\activate.bat

I am sure the venv is correctly activated since:

1. on the windows terminal, I see the command line is preceded by (my_venv)
2. if I activate python from the terminal (python) and run the following commands: import sys ; sys.path I can see, in the list of paths, the desired path [..., 'C:\\my_path\\my_venv\\lib\\site-packages\\win32\\lib', ...]
3. if I do stuff in the activated venv (like installing packages) everything works and is done inside the venv

To sum up, everything is fine so far.

I also have WSL2 (Ubuntu) and I'd like to activate the same venv using the Ubuntu terminal. If, from the Ubuntu terminal, I activate the venv

source /mnt/c/my_path/my_venv/Scripts/activate

it seems to work since the command line is preceeded by (my_venv), but when I run python (python3 command) and then run import sys ; sys.path I see that the system is targeting the base Ubuntu python installation (version 3.8) and not the venv installation:

['', '/usr/lib/python38.zip', '/usr/lib/python3.8', '/usr/lib/python3.8/lib-dynload', '/usr/local/lib/python3.8/dist-packages', '/usr/lib/python3/dist-packages']

The venv is not really activated. Any suggestions to solve the issue?

If it can help, I add a couple of information.

If I try to create a venv directly using the Ubuntu terminal

python3 -m venv /mnt/c/my_path/my_venv_unix

and activate it via the Ubuntu terminal (source /mnt/c/my_path/my_venv_unix/bin/activate) everything works fine, but that's not what I want: I'd like to use WSL to activate a virtual environment created using windows command prompt, since on my machine I've a lot of venvs created with windows and I don't want to replicate them.

Following the script C:\my_path\my_venv\Scripts\activate (/mnt/c/my_path/my_venv/Scripts/activate using wsl folders naming) (I had to change the EOL from windows to Ubuntu, otherwise the command source /mnt/c/my_path/my_venv/Scripts/activate would not have worked)

I set up my development environment on Fedora 35 and when I run any brownie command such as $ brownie console or even brownie --version I get the following error: