Closed WardBrian closed 1 year ago
I'd like to publish a 2.1.1 shortly after this, assuming nothing new comes in
Seems I can't easily test this PR directly in the nutpie CI, because checking out stan fails with a "path too long" error... https://github.com/pymc-devs/nutpie/actions/runs/5424318833/jobs/9863510219?pr=42#step:8:32
But this looks good to me, assuming tests pass.
fails with a "path too long" error...
Oh man, I recently dealt with this for Facebook's prophet package. Pip seems to like really long base path names, and a lot of the bash-on-Windows tools (including git, but also things like mingw32-make
), do not respect the LONG_PATHS setting and fail if the path is over ~280 characters. Super annoying
You may be able to get things going by setting %TEMPDIR%
to somewhere in the top-level of C:\
, but that might still be too long. Git cloning it somewhere and then pip install -e .
in that location would probably work.
@roualdes thoughts on this fix and a .1 release?
This does indeed fix the issue. I had to call the setup function manually though, loading the library failed without it.
Calling the setup function manually seems like a reasonable requirement for users who intend to load the dll not using the Python class we provide
Closes #148
This also adds a very trivial test: Can the package be imported without
BRIDGESTAN
being set ahead of time.