copy __init__.py to build dir#208
Conversation
This allows one to use something like ``` meson setup build && ninja -C build PYTHONPATH=build make check ``` to check using the current build. Without the `__init__.py` file in there, the system installation of cypari takes precedence.
Since this step takes significant time, so one knows what is going on. Note that while the autogen prints output as it goes, running it from `run_command()` hides the output. It is possible to capture the output and show it but only after it's finished. See: https://mesonbuild.com/Reference-manual_functions_run_command.html Note starting with meson 1.11 (unreleased) we could use `console: true`, but most likely we don't want to bump the meson requirement so soon.
|
@tobiasdiez does this look ok to you? My workflow is simpler with this. |
|
Also, perhaps we should move As it is, running |
|
BTW, is there a way so that running |
This is a good idea, and then you most likely don't need to copy the init file.
Yes, pytest can run doctests see https://docs.pytest.org/en/stable/how-to/doctest.html and https://github.com/lgpage/pytest-cython. But that likely requires a bit of tinkering. You can of course just run the |
I think we still need
Sure, but this means I need to know to run |
This allows one to use something like
to check using the current build.
Without the
__init__.pyfile in there, the system installation of cypari takes precedence.I also added a (trivial) commit to print a message before starting autogen, which takes a long time.