Skip to content

Conversation

@guptapratykshh
Copy link
Contributor

Description
This PR removes tox from the project's development and testing workflow. As mentioned in the issue, tox's ability to test multiple Python versions conflicts with the current GitHub Actions setup. It is also no longer actively used for local development.

This PR fixes #3526

Notes for Reviewers
The testing workflow is now fully standardized on pytest. Developers should use make test or uv run pytest.

Signed commits

  • Yes, I signed my commits.

Comment on lines 49 to 58

``make test-python-versions``
-----------------------------
The above command runs all tests under all currently supported versions of **Python 3.6 and above**.

Example\:

.. code-block:: bash

$ make test-python-versions
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we replace this with the command to run pytest?

find . -wholename build -delete
find . -wholename dist -delete
rm -rf .tox/

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we may want to keep this around for a bit with a comment explaining how it cleans up stuff that no longer exists.

if people heavily use the makefile and update, running clean after update wont remove any leftover .tox folders if they didnt clean before the update


.. _GitHub: https://github.com/chaoss/augur/issues

These commands are used to run specific subsets of unit tests. We use ``tox`` to manage the test environments, and ``pytest`` as the test runner. Each of these commands except for ``make test-pythons-versions`` will use your default Python version, while ``make test-python-versions`` will test all supported Python versions.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good catch! i forgot to update the docs in my version of this

@MoralCode MoralCode added the waiting This change is waiting for some other changes to land first label Jan 8, 2026
@MoralCode
Copy link
Contributor

Something to note is that, even though its an "issue" in the github sense, the issue behind this wasnt really intended to be fixed just yet as im still waiting to give the maintainers a chance to object.

That said, this is still helpful, but im going to mark it as waiting for now

@guptapratykshh guptapratykshh force-pushed the fix/remove-tox branch 2 times, most recently from 74cc91d to d48572e Compare January 9, 2026 05:33
@guptapratykshh
Copy link
Contributor Author

Thanks for the update. I understand this is waiting for a final decision. I have made the requested updates by replacing the outdated make target documentation with direct pytest instructions. I also made sure the clean script handles .toxcleanup. The PR is ready whenever you decide to move forward.

@MoralCode MoralCode marked this pull request as draft January 9, 2026 20:08
@MoralCode MoralCode marked this pull request as ready for review February 4, 2026 17:17
@MoralCode
Copy link
Contributor

Will review/merge this in 72 hours if my followup on a decision remains unanswered.

Could you rebase this in the meantime?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

waiting This change is waiting for some other changes to land first

Projects

None yet

Development

Successfully merging this pull request may close these issues.

RFC: Remove tox from unit testing workflow

2 participants