You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The difference here is that the functions code is in a /src folder, a folder deeper than the .venv. This works fine except in VSCode when I'm testing, func host start doesn't find the .venv because it's in the parent folder. It works in a command prompt when I start the virtual env manually then enter src/ and run func host start.
I want to keep tests separate so they don't ship with my production code and the structure mirrors the layout we'd like to use elsewhere in our Monorepo.
Is there either a way when running func host start to specify a path for my virtual env or the root path of my function app?
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.
I'd like to use a slightly different structure than the standard Python folder structure for functions.
The difference here is that the functions code is in a /src folder, a folder deeper than the .venv. This works fine except in VSCode when I'm testing,
func host start
doesn't find the.venv
because it's in the parent folder. It works in a command prompt when I start the virtual env manually then enter src/ and runfunc host start
.I want to keep tests separate so they don't ship with my production code and the structure mirrors the layout we'd like to use elsewhere in our Monorepo.
Is there either a way when running
func host start
to specify a path for my virtual env or the root path of my function app?The text was updated successfully, but these errors were encountered: