. e don't pass environment to tox

[JayBazuzi]

tox (with no arguments), appears to do the right thing. Specifically:

• tox -e py appears to run testenv
• just tox runs everything in envlist which is tests, which magically resolves to testenv

The latter seems better, as it lets us make use of envlist.

Here's a screenshot from the GitHub actions showing that tests are still being run with this change:

Summary by Sourcery

Enhancements:

• Remove unnecessary environment variable passing to tox in the test script.

[sourcery-ai]

Reviewer's Guide by Sourcery

The PR removes the environment specification (-e py) from the tox command in the test runner script, allowing tox to use its default environment configuration.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Simplified tox test execution by removing explicit environment specification	Removed '-e py' parameter from tox command Allows tox to use default environment configuration from tox.ini	run_tests.sh

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.