[builddeps] Activate pytest plugin for Celery #138
No reviewers
Labels
No labels
Security
TeX
board
done
board
ready
board
todo
part
backend
part
ci
part
docs
part
frontend
part
i18n
part
non-technical
part
packaging
prio
1
prio
2
prio
3
release-mr-5.x
size
large
size
medium
size
small
source
customer
source
customer::fsmw
source
customer::fss
source
customer::teckids
source
downstream
type
breaking
type
bug
type
feature
type
refactoring
workflow
blocked
workflow
confirmed
workflow
current-todo
workflow
discussing
workflow
new-app
workflow
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
aleksis/AlekSIS!138
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "active-pytest-celery"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I had to set an explicit version for the Python dependency because otherwise the black and isort dependencies caused resolver errors.
Please fix the resolver error instead of adding an unnecessarily explicit dependency.
If someone could explain this error to me, that would be an option, of course:
This dependency is unnecessary.
I don't think we should depend on this, given that this library has not yet been released and seems unmaintained in general.
According to the documentation at https://docs.celeryproject.org/en/stable/userguide/testing.html, we also could add
celery[pytest], but that also results in the installation of the meta packagepytest-celery.The interesting part is where this additiona
<3.6comes from.However, as this dependency is entirely useless, I recommend going without it instead of debugging this issue.
According to the documentaiton, we could also just set
PYTEST_PLUGINS=celery.contrib.pytestin the environment, instead of bloating our dependencies to do just that.In which environment?
The environment, as in https://pubs.opengroup.org/onlinepubs/009696899/basedefs/xbd_chap08.html
Yes, of course, but you don't want to rely on each user to set their environment variables correctly, do you?
Do you want to add this variable in the
tox.inifile?I knew you'd figure it out ☺!
(Or use the
conftest.pymechanism. I will leave that up to you…Pull request closed