Skip to content

5.0.0: pytest warnings #7

Open
Open

Description

@kloczek
+ PYTHONPATH=/home/tkloczko/rpmbuild/BUILDROOT/python-fields-5.0.0-10.fc35.x86_64/usr/lib64/python3.8/site-packages:/home/tkloczko/rpmbuild/BUILDROOT/python-fields-5.0.0-10.fc35.x86_64/usr/lib/python3.8/site-packages
+ PYTHONDONTWRITEBYTECODE=1
+ /usr/bin/pytest -ra
=========================================================================== test session starts ============================================================================
platform linux -- Python 3.8.9, pytest-6.2.4, 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/python-fields-5.0.0, configfile: setup.cfg
plugins: forked-1.3.0, shutil-1.7.0, virtualenv-1.7.0, expect-1.1.0, httpbin-1.0.0, xdist-2.2.1, flake8-1.0.7, timeout-1.4.2, betamax-0.8.1, freezegun-0.4.2, case-1.5.3, isort-1.3.0, aspectlib-1.5.2, asyncio-0.15.1, toolbox-0.5, xprocess-0.17.1, aiohttp-0.3.0, checkdocs-2.7.0, mock-3.6.1, rerunfailures-9.1.1, requests-mock-1.9.3, cov-2.12.1, pyfakefs-4.5.0, cases-3.6.1, flaky-3.7.0, hypothesis-6.14.0, benchmark-3.4.1, Faker-8.8.0
collected 170 items

README.rst .                                                                                                                                                         [  0%]
. .                                                                                                                                                                  [  1%]
src/fields/__init__.py .                                                                                                                                             [  1%]
tests/test_fields.py ............................................................................................................................................... [ 85%]
..............                                                                                                                                                       [ 94%]
tests/test_perf.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
====================================================================== 170 passed, 1 warning in 7.59s ======================================================================

And ..

[tkloczko@barrel python-fields-5.0.0]$ grep -r strict setup.cfg
    --strict

Activity

  1. kloczek commented on Jun 15, 2021

    @kloczek
    Author

    BTW: to use latest pytest it is necessaty to fix setup.cfg

    --- a/setup.cfg~        2016-04-13 21:51:23.000000000 +0100
    +++ b/setup.cfg 2021-06-15 20:52:05.889359421 +0100
    @@ -8,7 +8,7 @@
     max-line-length = 140
     exclude = tests/*,*/migrations/*,*/south_migrations/*
    
    -[pytest]
    +[tools:pytest]
     norecursedirs =
         .git
         .tox
  2. added a commit that references this issue on Aug 26, 2021
  3. ionelmc commented on Aug 26, 2021

    @ionelmc
    Owner

    Fixed now.

  4. kloczek commented on Aug 26, 2021

    @kloczek
    Author

    Cannot test that patch because it needs other patches.
    Will try to confirm that everything is ok on next release (hopefully it will be soon :))

  5. ionelmc commented on Aug 26, 2021

    @ionelmc
    Owner

    What would I release? There's no new feature, just cruft :)

    What other changes do you need? Or you have previous patches that don't apply cleanly anymore?

  6. kloczek commented on Aug 27, 2021

    @kloczek
    Author

    No .. simple that commit looks like conmtains a lot of cleanups :)

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions