Files
aitbc/.gitea/workflows
aitbc1 d186ce03b4
Some checks failed
audit / audit (push) Failing after 3s
ci-cd / build (push) Failing after 6s
ci / build (push) Failing after 3s
autofix / fix (push) Failing after 1s
security-scanning / audit (push) Failing after 2s
test / test (push) Successful in 1s
ci-cd / deploy (push) Has been skipped
fix: use virtual environment to resolve externally-managed-environment
PROGRESS: Python project detected, but hitting PEP 668 restriction

Issue: 'externally-managed-environment' - Debian protects system Python
Root cause: Modern Python installations prevent system-wide pip installs
Solution: Use virtual environment (proper Python best practice)

Changes:
- Add python3-full to package installation
- Create virtual environment: python3 -m venv venv
- Activate venv: source venv/bin/activate
- Install poetry and dependencies inside venv
- Run security tools in isolated environment

Updated workflows:
- audit.yml: Virtual environment + poetry install + audit
- fix.yml: Virtual environment + poetry install + safety fixes
- security-scanning.yml: Virtual environment + poetry install + security scans

Expected results:
- Virtual environment created and activated
- Poetry installed without system restrictions
- Dependencies installed in isolated environment
- Security tools (safety, bandit) working properly
- All workflows should complete successfully

This follows Python best practices and resolves PEP 668 restrictions
while maintaining the nuclear fix for workspace control.
2026-03-27 12:58:42 +01:00
..