sphinx-contrib / sphinx-contrib/openapi
0.7.0: pytest warning
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 126
- Forks
- 88
- PR merge metrics
- No merged PRs in 30d
Description
I'm trying to package your module as an rpm package. So I'm using the typical build, install and test cycle used on building packages from non-root account.
- "setup.py build"
- "setup.py install --root </install/prefix>"
- "pytest with PYTHONPATH pointing to sitearch and sitelib inside </install/prefix>
+ PYTHONPATH=/home/tkloczko/rpmbuild/BUILDROOT/python-sphinxcontrib-openapi-0.7.0-4.fc35.x86_64/usr/lib64/python3.8/site-packages:/home/tkloczko/rpmbuild/BUILDROOT/python-sphinxcontrib-openapi-0.7.0-4.fc35.x86_64/usr/lib/python3.8/site-packages
+ /usr/bin/pytest -ra --import-mode=importlib tests/ --strict -p no:randomly
=========================================================================== test session starts ============================================================================
platform linux -- Python 3.8.11, pytest-6.2.5, py-1.10.0, pluggy-0.13.1
benchmark: 3.4.1 (defaults: timer=time.perf_counter disable_gc=False min_rounds=5 min_time=0.000005 max_time=1.0 calibration_precision=10 warmup=False warmup_iterations=100000)
rootdir: /home/tkloczko/rpmbuild/BUILD/openapi-0.7.0
plugins: forked-1.3.0, shutil-1.7.0, virtualenv-1.7.0, expect-1.1.0, flake8-1.0.7, timeout-1.4.2, betamax-0.8.1, freezegun-0.4.2, aspectlib-1.5.2, toolbox-0.5, rerunfailures-9.1.1, requests-mock-1.9.3, cov-2.12.1, flaky-3.7.0, benchmark-3.4.1, xdist-2.3.0, pylama-7.7.1, datadir-1.3.1, regressions-2.2.0, cases-3.6.3, xprocess-0.18.1, black-0.3.12, anyio-3.3.0, asyncio-0.15.1, trio-0.7.0, subtests-0.5.0, isort-2.0.0, hypothesis-6.14.6, mock-3.6.1, profiling-1.7.0, Faker-8.12.1, nose2pytest-1.0.8, pyfakefs-4.5.1, tornado-0.8.1, twisted-1.13.3
collected 223 items
tests/test_openapi.py ................................. [ 14%]
tests/test_schema_utils.py ......... [ 18%]
tests/test_spec_examples.py ......... [ 22%]
tests/renderers/httpdomain/test_render_operation.py ............. [ 28%]
tests/renderers/httpdomain/test_render_parameter.py .......................................... [ 47%]
tests/renderers/httpdomain/test_render_parameters.py ............. [ 53%]
tests/renderers/httpdomain/test_render_paths.py ......... [ 57%]
tests/renderers/httpdomain/test_render_request_body_example.py ......................... [ 68%]
tests/renderers/httpdomain/test_render_response.py .................................... [ 84%]
tests/renderers/httpdomain/test_render_response_content.py .............................. [ 98%]
tests/renderers/httpdomain/test_render_responses.py .... [100%]
============================================================================= warnings summary =============================================================================
../../../../../usr/lib/python3.8/site-packages/_pytest/config/__init__.py:1183
/usr/lib/python3.8/site-packages/_pytest/config/__init__.py:1183: PytestDeprecationWarning: The --strict option is deprecated, use --strict-markers instead.
self.issue_config_time_warning(
-- Docs: https://docs.pytest.org/en/stable/warnings.html
====================================================================== 223 passed, 1 warning in 3.54s ======================================================================
pytest-xprocess reminder::Be sure to terminate the started process by running 'pytest --xkill' if you have not explicitly done so in your fixture with 'xprocess.getinfo(<process_name>).terminate()'.
BTW test suite. Looks like test suite needs only two files from OpenAPI-Specification: tests/OpenAPI-Specification/examples/v3.0/petstore.yaml and tests/OpenAPI-Specification/examples/v2.0/json/uber.json.
Is it not would be easier to just copy those two files into git repo instead linking submodule?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the pytest command and the test-suite references to the OpenAPI-Specification submodule. Confirm whether the deprecated --strict warning comes from project configuration or the packaging test invocation, and assess whether tests/OpenAPI-Specification/examples/v3.0/petstore.yaml and tests/OpenAPI-Specification/examples/v2.0/json/uber.json can be copied into the repository without breaking the suite.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi, python
- Domain
- build-system, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100