Simple `pyoxidizer build` Failing on Windows when Path Contains Spaces

This might be due to spaces in my paths, but pyoxidizer build fails for me on Windows 10:

C:\Users\WolfgangRichter\OneDrive - {REDACTED}\Development\oxidizer-test>pyoxidizer build
thread 'main' panicked at 'unable to get directory entry: Error { depth: 16, inner: Io { path: Some("C:/Users/WolfgangRichter/OneDrive - {REDACTED}/Development/oxidizer-test\\build\\target\\x86_64-pc-windows-msvc\\debug\\pyoxidizer\\python.fd43554b5654\\python\\install\\Lib\\site-packages\\pip-19.1.1-py3.7.egg\\pip\\_vendor\\cachecontrol\\caches\\__pycache__"), err: Os { code: 3, kind: NotFound, message: "The system cannot find the path specified." } } }', src\libcore\result.rs:997:5
stack backtrace:
   0: git_packbuilder_object_count
   1: git_packbuilder_object_count
   2: git_packbuilder_object_count
   3: git_packbuilder_object_count
   4: git_packbuilder_object_count
   5: git_packbuilder_object_count
   6: git_packbuilder_object_count
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: <unknown>
  15: git_packbuilder_object_count
  16: git_packbuilder_object_count
  17: git_packbuilder_object_count
  18: <unknown>
  19: git_libgit2_version
  20: BaseThreadInitThunk
  21: RtlUserThreadStart

The reported entry point is pyoxidizer build on Windows 10 with a project path containing spaces; first reproduce it in that setup and inspect the directory traversal that emits the missing-path panic. Done means the command completes successfully from a spaced path without the reported panic.