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
I've tried two modes for building the binary: using the dependency file and using a wheel file with the PYAPP_PROJECT_PATH setting.
When I use the embedding option, the dependencies sometimes don’t match exactly with my local lock/requirements file, which makes sense since the wheel file's dependency markers don’t use exact versions (==). With the dependency file option, it seems I would need my app to be available on PyPI or something similar. Is there a way to use both the wheel file and a requirements file so that the environment created by the binary matches exactly what I have locally? I tried setting both PYAPP_PROJECT_PATH and PYAPP_PROJECT_DEPENDENCY_FILE, but it seems the requirements file is ignored in this case.
The text was updated successfully, but these errors were encountered:
I've tried two modes for building the binary: using the dependency file and using a wheel file with the
PYAPP_PROJECT_PATH
setting.When I use the embedding option, the dependencies sometimes don’t match exactly with my local lock/requirements file, which makes sense since the wheel file's dependency markers don’t use exact versions (
==
). With the dependency file option, it seems I would need my app to be available on PyPI or something similar. Is there a way to use both the wheel file and a requirements file so that the environment created by the binary matches exactly what I have locally? I tried setting bothPYAPP_PROJECT_PATH
andPYAPP_PROJECT_DEPENDENCY_FILE
, but it seems the requirements file is ignored in this case.The text was updated successfully, but these errors were encountered: