On Tue, 22 Aug 2023 at 22:32, Karen Róbertsdóttir < karen.robertsdottir@gmail.com> wrote:
On that note I tried setting up the dev environment, on a new branch. After two hours of work I got it built. But now I can neither rebuild it nor run tests:
I'm sorry that the build is hard to do. The scipy webpage has some information on how to build, https://docs.scipy.org/doc/scipy-1.10.1/dev/dev_quickstart.html. You shouldn't have to rebuild time after time, you should just be able to run `python dev.py test`, tweak, `python dev.py test` without having to do anything else. In this circumstance I might suggest removing the build and build-install directories and just running `python dev.py test` multiple times. Unless you want to specify specific BLAS libraries you shouldn't have to use any flags. If you're on Linux, you can just install system BLAS.
scipy]$ python dev.py test -v 💻 ninja -C /path/to/scipy/build -j6 ninja: Entering directory `/path/to/scipy/build' [4/4] Generating scipy/generate-version with a custom command Build OK Task Error - build => PythonAction Error ╭────────────────────────────────────────────────────────────────────────────────────────────────────────────────── build ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮ │ Traceback (most recent call last):
│ │ File "/path/to/.local/lib/python3.10/site-packages/doit/action.py", line 461, in execute
│ │ returned_value = self.py_callable(*self.args, **kwargs)
│ │ File "/path/to/scipy/dev.py", line 668, in run
│ │ cls.install_project(dirs, args)
│ │ File "/path/to/scipy/dev.py", line 533, in install_project
│ │ raise RuntimeError("Can't install in non-empty directory: "
│ │ RuntimeError: Can't install in non-empty directory: '/path/to/scipy/build-install'
│ │
│ ╰─────────────────────────────────────────────────────────────────────────────────────────────────────────── PythonAction Error ────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
Does it expect me to manually delete the build directory every time, or what? If so, that may raise a problem, because I had to build with "*python dev.py build -C-Dblas=blas -C-Dlapack=lapack"*, but it refuses to take those -C options with "python dev.py test -v". Honestly, it's strange that "test" would insist on the build directory being nonexistent in the first place. Perhaps I'm misunderstanding something.
- kv, Karen
_______________________________________________
SciPy-Dev mailing list -- scipy-dev@python.org To unsubscribe send an email to scipy-dev-leave@python.org https://mail.python.org/mailman3/lists/scipy-dev.python.org/ Member address: karen.robertsdottir@gmail.com
_______________________________________________ SciPy-Dev mailing list -- scipy-dev@python.org To unsubscribe send an email to scipy-dev-leave@python.org https://mail.python.org/mailman3/lists/scipy-dev.python.org/ Member address: andyfaff@gmail.com
-- _____________________________________ Dr. Andrew Nelson _____________________________________