`quix local init` seems to behave strangely when there's a virtualenv.

[krisajenkins]

When I run quix local init in a project that uses virtualenv, it creates some files in extremely odd places:

» mkdir quix-local-init-check
» cd quix-local-init-check
quix-local-init-check » git init
Initialized empty Git repository in .../quix-local-init-check/.git/

quix-local-init-check » mkdir someapp
quix-local-init-check » cd someapp

someapp » python3 -m venv env
someapp » quix local init

Created dockerfile in 
.../quix-local-init-check/someapp/env/lib/python3.12/site-packages/pip/_internalCreated dockerfile in 
.../quix-local-init-check/someapp/env/lib/python3.12/site-packages/pip/_internal/cliCreated app.yaml in 
'.../quix-local-init-check/someapp/env/lib/python3.12/site-packages/pip/_internal'
Created app.yaml in 
'.../quix-local-init-check/someapp/env/lib/python3.12/site-packages/pip/_internal/cli'
Created default quix.yaml
Created .gitignore with .env and .venv/ entries
quix-local-init-check/someapp » 

That can't be the expected behaviour, can it?

Platform: OSX
Quix CLI version: 0.0.1-20240322.1+4e718a63938e405fdd09ac345f72794ec5b3ebbf

[emanuel-quix]

It's not an expected behavior indeed, we will look into it, thank you!

[luisquix]

This issue has been fixed.