aitbc1 aed22b7d8b fix: use pipx for poetry + venv for project dependencies ...

SOLUTION: Hybrid approach using pipx + virtual environment

Strategy:
- pipx: Install poetry (manages its own virtual environment)
- venv: Isolate project dependencies and security tools
- This avoids PEP 668 restrictions completely

Changes:
- Install pipx system-wide for poetry management
- Use 'pipx install poetry' (bypasses system pip restrictions)
- Create separate venv for project dependencies
- Use poetry (via pipx) to install project dependencies
- Use venv/bin/pip for security tools (safety, bandit)
- Maintain complete isolation for both environments

Benefits:
- Poetry: Self-contained virtual environment via pipx
- Project: Isolated dependencies in project venv
- Security: Tools in project venv for consistency
- No conflicts: Complete separation of concerns
- PEP 668 compliant: No system Python modifications

Updated workflows:
- audit.yml: pipx poetry + project venv
- fix.yml: pipx poetry + project venv + safety
- security-scanning.yml: pipx poetry + project venv + security tools

Expected results:
- Poetry installed via pipx without system restrictions
- Project dependencies installed via poetry in project venv
- Security tools working in isolated project venv
- Complete compliance with PEP 668 requirements
- All workflows should complete successfully

2026-03-27 13:17:29 +01:00

..

ISSUE_TEMPLATE

fix: set proper Gitea issue template for agent tasks

2026-03-15 22:53:48 +00:00

workflows

fix: use pipx for poetry + venv for project dependencies

2026-03-27 13:17:29 +01:00