? Do you have files named
? These will cause conflicting imports
into the venv?
there and try running that?
as much so I’d have to ask the team tomorrow, but this might also be because the script you have is inside the
. It might also be worth trying to have the script in the directory above
, but still have the
activated. If this also fails, I would look at your path and see if there is a folder in your path that has a folder named
that can cause the import conflict