[1] https://manpages.debian.org/testing/dh-python/pybuild.1.en.html
On Thu, Oct 31, 2024 at 06:22:45PM +0100, John Paul Adrian Glaubitz wrote:
(Please CC me as I'm not subscribed to this list)
Hello,
I need to override the standard test for pybuild and according to the manpage [1]
this is achieved by passing "--test-custom" to pybuild. Unfortunately, it's actually
not saying where exactly the parameter needs to go.
I tried setting it via "export PYBUILD_OPTION=" but that didn't work.
export PYBUILD_TEST_CUSTOM = 1
export PYBUILD_TEST_ARGS = <custom test command>
[1] https://github.com/p1otr/dh-python/blob/c5a56cdf8cf24b11ac68c980937cf0ef0921d2e0/README.rst#L104
[2] https://wiki.debian.org/Python/Pybuild
(Please CC me as I'm not subscribed to this list)
Hello,
I need to override the standard test for pybuild and according to the manpage [1]
this is achieved by passing "--test-custom" to pybuild. Unfortunately, it's actually
not saying where exactly the parameter needs to go.
I tried setting it via "export PYBUILD_OPTION=" but that didn't work.
(Please CC me as I'm not subscribed to this list)
Hello,
I need to override the standard test for pybuild and according to the manpage [1]
this is achieved by passing "--test-custom" to pybuild. Unfortunately, it's actually
not saying where exactly the parameter needs to go.
I tried setting it via "export PYBUILD_OPTION=" but that didn't work.
export PYBUILD_TEST_CUSTOM = 1
export PYBUILD_TEST_ARGS = <custom test command>
Thanks a lot. I would have never guessed that.
Thanks a lot. I would have never guessed that.
(see "Most options can be set (in addition to command line) via
environment variables." in "OPTIONS")
Hi Julian,
[...]
Thanks a lot. I would have never guessed that.
Meanwhile, I found the following alternative approach in the README.rst [1]:
dh_auto_test -- --system=custom --test-args='{interpreter} setup.py test'
Your suggestion looks cleaner. If it works, I'll use it. If not, I'll stick to the
approach above as it actually works. Took me forever to figure this all out.
I think this information could be added to the Pybuild page on the Debian wiki [2].
Hi Adrian,
On Thu, Oct 31, 2024 at 07:08:20PM +0100, John Paul Adrian Glaubitz wrote:
Hi Julian,
[...]
Thanks a lot. I would have never guessed that.
Meanwhile, I found the following alternative approach in the README.rst [1]: >>
dh_auto_test -- --system=custom --test-args='{interpreter} setup.py test'
Your suggestion looks cleaner. If it works, I'll use it. If not, I'll stick to the
approach above as it actually works. Took me forever to figure this all out. >>
I think this information could be added to the Pybuild page on the Debian wiki [2].
Sounds a great idea; please feel free to edit the page to include
this!
Hi Julian,
On Thu, 2024-10-31 at 17:57 +0000, Julian Gilbey wrote:
On Thu, Oct 31, 2024 at 06:22:45PM +0100, John Paul Adrian Glaubitz wrote:
(Please CC me as I'm not subscribed to this list)
Hello,
I need to override the standard test for pybuild and according to the manpage [1]
this is achieved by passing "--test-custom" to pybuild. Unfortunately, it's actually
not saying where exactly the parameter needs to go.
I tried setting it via "export PYBUILD_OPTION=" but that didn't work.
export PYBUILD_TEST_CUSTOM = 1
export PYBUILD_TEST_ARGS = <custom test command>
Thanks a lot. I would have never guessed that.
Meanwhile, I found the following alternative approach in the README.rst [1]:
dh_auto_test -- --system=custom --test-args='{interpreter} setup.py test'
Your suggestion looks cleaner. If it works, I'll use it. If not, I'll stick to the
approach above as it actually works. Took me forever to figure this all out.
On 31.10.24 21:53, Julian Gilbey wrote:
Hi Adrian,
[...]
I think this information could be added to the Pybuild page on the Debian wiki [2].
Sounds a great idea; please feel free to edit the page to include
this!
sorry, but this feels like a bullshit comment. pun intended.
the pybuild information really is not adequate. but requesting people having questions to just add another tiny improvement to this kind of documentation is not helping very much. So maybe the people already knowing all the
quirks could come up with a way to rewrite the docs?
We even could have that as the first topic for a Python BoF, before starting any other topic ...
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 481 |
Nodes: | 16 (2 / 14) |
Uptime: | 32:28:20 |
Calls: | 9,546 |
Calls today: | 6 |
Files: | 13,656 |
Messages: | 6,141,056 |