Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 26 |
Nodes: | 6 (0 / 6) |
Uptime: | 57:02:23 |
Calls: | 632 |
Files: | 1,188 |
D/L today: |
28 files (19,987K bytes) |
Messages: | 179,886 |
Nuno Teixeira wrote:ay.
Hello,
Just found that PYTEST_ARGS isn't respected when pytest is placed in USE_PYTHON instead of USES. pytest.mk <http://pytest.mk> could be misleading pointing its correct place in USES as I remember a big discussion about it long time ago. Anyway, I see no other python port
using PYTEST_ARGS for comparison, I see that some ports uses pytest on
both places and certainly I've spoted a bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D289005 <https:// bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D289005>
USES=3Dpytest should not be used in general; USE_PYTHON=3Dpytest is the w=
There is currently no support for ${PYTEST_ARGS} in USES=3Dpython as
pytest has its own entry point, rather than pointing to arbitrary
file(s) for said entry point like the referenced port/bug.
--
Charlie Li
...nope, still don't have an exit line.
<br></div><div>Thanks,</div></div><br><div class=3D"gmail_quote gmail_quo= te_container"><div dir=3D"ltr" class=3D"gmail_attr">Charlie Li <<a href= =3D"mailto:vishwin@freebsd.org">vishwin@freebsd.org</a>> escreveu (quart=a, 3/09/2025 =C3=A0(s) 22:00):<br></div><blockquote class=3D"gmail_quote" s= tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad= ding-left:1ex">Nuno Teixeira wrote:<br>
Nuno Teixeira wrote:
Hello Charlie,
Sorry but I didn't understanded your explanation.
What we got is that if I'll do the following changes to port: comms/py- streamdeck, PYTEST_ARGS isn't respected:
- USES=3D dos2unix pytest python
+ USES=3D dos2unix python
- USE_PYTHON=3D autoplist pep517
+ USE_PYTHON=3D autoplist pep517 pytest
PYTEST_ARGS=3D test.py
${PYTEST_ARGS} is not respected with USE_PYTHON=3Dpytest because ${PYTEST_ARGS} is not used at all. USE_PYTHON=3Dpytest executes pytest directly, with the only arguments dealing with individual tests to skip.
This particular port/package does not use or mention pytest at all, so
it is wrong to have pytest specified. The correct way here is to define do-test to execute test.py.
--
Charlie Li
...nope, still don't have an exit line.
It does.:38):
setup.py:
#!/usr/bin/env python3
# Python Stream Deck Library
# Released under the MIT license
#
# dean [at] fourwalledcubicle [dot] com
# www.fourwalledcubicle.com
#
import argparse
import logging
import os
import sys
sys.path.insert(0, os.path.join(os.path.dirname(__file__), '../src'))
from StreamDeck.DeviceManager import DeviceManager
from StreamDeck.ImageHelpers import PILHelper
from PIL import ImageDraw
import pytest
<snip>
Charlie Li <vishwin@freebsd.org> escreveu (quinta, 4/09/2025 =C3=A0(s) 21=
-Nuno Teixeira wrote:
Hello Charlie,
Sorry but I didn't understanded your explanation.
What we got is that if I'll do the following changes to port: comms/py=
streamdeck, PYTEST_ARGS isn't respected:${PYTEST_ARGS} is not respected with USE_PYTHON=3Dpytest because
- USES=3D dos2unix pytest python
+ USES=3D dos2unix python
- USE_PYTHON=3D autoplist pep517
+ USE_PYTHON=3D autoplist pep517 pytest
PYTEST_ARGS=3D test.py
${PYTEST_ARGS} is not used at all. USE_PYTHON=3Dpytest executes pytest
directly, with the only arguments dealing with individual tests to skip.
This particular port/package does not use or mention pytest at all, so
it is wrong to have pytest specified. The correct way here is to define
do-test to execute test.py.
--
Charlie Li
...nope, still don't have an exit line.
--
Nuno Teixeira
FreeBSD UNIX: <eduardo@FreeBSD.org> Web: https://FreeBSD.org