Dependency file is not a file: ./requirements.txt

Thanks a lot for developing this project! I am very excited to try it.

I wanted to use it with a simple example project using poetry. I am trying to do it on Windows and have the following powershell file (build_with_pyapp.ps1).

# Export poetry requirements to requirements.txt
poetry export -f requirements.txt --output requirements.txt
# Now set environment variables properly in powershell
$env:PYAPP_PROJECT_VERSION="0.1.0"
$env:PYAPP_PROJECT_NAME="pyappexample"
$env:PYAPP_PROJECT_DEPENDENCY_FILE="./requirements.txt"
$env:CARGO_TARGET_DIR="./target" # For speeding up future builds
$env:PYAPP_EXEC_SCRIPT="./pyappexample/circle.py"
cargo install pyapp

Unfortunately I am getting the following error:

[<compiling stuff...>]
error: failed to run custom build command for `pyapp v0.13.0`

Caused by:
  process didn't exit successfully: `C:\Users\hanne\Documents\Programme\pyappexample\./target\release\build\pyapp-7c9fbca43121c7ae\build-script-build` (exit code: 101)
  --- stdout
  cargo:rustc-env=PYAPP_PROJECT_NAME=pyappexample
  cargo:rustc-env=PYAPP_PROJECT_VERSION=0.1.0

  --- stderr
  thread 'main' panicked at C:\Users\hanne\.cargo\registry\src\index.crates.io-6f17d22bba15001f\pyapp-0.13.0\build.rs:389:9:       


  Dependency file is not a file: ./requirements.txt


  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: failed to compile `pyapp v0.13.0`, intermediate artifacts can be found at `C:\Users\hanne\Documents\Programme\pyappexample\./target`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.
(pyappexample-py3.10) PS C:\Users\hanne\Documents\Programme\pyappexample> 

I am executing the powershell script from the root directory, where my requirements.txt file is located.

Have a great day!

Start with build.rs around line 389, where the reported “Dependency file is not a file” error is raised, and reproduce the PowerShell invocation from the project root. Trace how ./requirements.txt is resolved during the cargo install pyapp build; done means the shown Windows command accepts the existing requirements.txt.