René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[FEAT] Add tox-based testing environment for OpenStack users","articleBody":"## Summary\n\nAdd `tox` configuration following OpenStack standards while keeping `uv` for development.\n\n## Motivation\n\nMost OpenStack projects use `tox` for testing and CI/CD. Our project should follow these standards to be familiar to OpenStack contributors.\n\n**Use cases:**\n- Run tests: `tox -e py3` or `tox -e py310`\n- Run linting: `tox -e pep8`\n- Generate coverage: `tox -e cover`\n- Build docs: `tox -e docs`\n- Run in venv: `tox -e venv -- \u003ccommand\u003e`\n\n## Proposal\n\nAdd `tox.ini` following OpenStack SDK patterns:\n- Basic environments: `py3`, `py{310,311,312}`\n- Linting: `pep8` (using ruff instead of flake8)\n- Coverage: `cover`\n- Venv: `venv` for arbitrary commands\n- Consider using `tox-uv` plugin for performance while keeping OpenStack-style configuration\n\nKeep existing `uv` workflow for fast local development.\n\n## Additional context\n\nReference: [openstacksdk tox.ini](https://github.com/openstack/openstacksdk/blob/master/tox.ini)\n\nRelated to #76 - Supporting various package managers for common OpenStack users.","author":{"url":"https://github.com/paikend","@type":"Person","name":"paikend"},"datePublished":"2025-10-25T13:49:15.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/99/python-openstackmcp-server/issues/99"}