-
Notifications
You must be signed in to change notification settings - Fork 431
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update test suite to use pytest, remove related in setup.py #771
Update test suite to use pytest, remove related in setup.py #771
Conversation
Running |
Nice initiative!! This is still happening on our GitHub Actions Py3.12 tests...
In this repo: Line 142 in 8fe7836
|
If anyone wants to take over and continue fixing, please do so.. |
Is this the right way to install a branch? Is it not
Edit: Sorry I think i must be missing something... |
Co-authored-by: Christian Clauss <cclauss@me.com>
for more information, see https://pre-commit.ci
pip3 install django-celery-beat@git+https://github.com/kwongtn/django-celery-beat.git@fix/restrict-setuptools-to-max-v71 Collecting django-celery-beat@ git+https://github.com/kwongtn/django-celery-beat.git@fix/restrict-setuptools-to-max-v71 × Getting requirements to build wheel did not run successfully. note: This error originates from a subprocess, and is likely not a problem with pip. the code should be removed?
|
@shijl0925 Yup I think you're right -- removed it and it works nicely now Not sure how it will affect the test in this repo tho 😅 I'll be locking my prod build to 65d5743 , but @cclauss feel free to make required edits |
@@ -139,7 +139,7 @@ test-all: clean-pyc | |||
$(TOX) | |||
|
|||
test: | |||
$(PYTHON) setup.py test | |||
$(PYTHON) -m $(PYTEST) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does make test
work on your machine?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately no, but tox
does though
Although t/unit/test_schedulers.py::test_modeladmin_PeriodicTaskAdmin::test_run_task
fail 😅
Please try |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* Fix setuptools to <v72 * Makefile: Use pytest instead of setup.py test * Attempt to use pytest directly * Add python -m * Update setup.py Co-authored-by: Christian Clauss <cclauss@me.com> * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci * Add pytest installation to workflow * Remove pytest from setup.py * Unlock setuptools * Remove tests_require * Move pytest to tox.ini --------- Co-authored-by: Christian Clauss <cclauss@me.com> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> (cherry picked from commit a50011d)
Setuptools removes use of
setuptools.command.test
This PR serves as a quick temporary fix.
Refer: