Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New pip venv BS #1887

Open
hwac121 opened this issue Sep 27, 2024 · 4 comments
Open

New pip venv BS #1887

hwac121 opened this issue Sep 27, 2024 · 4 comments

Comments

@hwac121
Copy link

hwac121 commented Sep 27, 2024

Is there a work around to avoid this new pip venv crap that breaks "pip install -r requirements.txt" installs?

@yelrom0
Copy link

yelrom0 commented Sep 28, 2024

It seems to be an issue with the version of PyYaml, specifically building the binary wheels. If you change the PyYaml version in requirements.txt to the version on the master branch pyyaml>=6.0.0,<7 it will install (at least it did for me).

I haven't had the opportunity to look into it further and test spiderfoot stable thoroughly with this version of pyyaml, I will update accordingly once I do.

@DinoDavidRaptor
Copy link

pip install setuptools
pip3 install --no-build-isolation "pyyaml==5.4.1"
pip install -r requirements.txt

@bcoles
Copy link
Contributor

bcoles commented Oct 4, 2024

Is there a work around to avoid this new pip venv crap that breaks "pip install -r requirements.txt" installs?

If you want to use venv rather than work around it:

python3 -m venv venv
./venv/bin/pip3 install -r requirements.txt
./venv/bin/python3 ./sf.py -l 127.0.0.1:5001

@DinoDavidRaptor
Copy link

Is there a work around to avoid this new pip venv crap that breaks "pip install -r requirements.txt" installs?

If you want to use venv rather than work around it:

python3 -m venv venv
./venv/bin/pip3 install -r requirements.txt
./venv/bin/python3 ./sf.py -l 127.0.0.1:5001

The problem doesn't has nothing to do with the environment, it's the PyYAML module, so even if you try to install it through a virtual environment it will still being the same problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants