question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

1.18.23: test suite uses outdated `nose` module

See original GitHub issue

nose is no longer maintained since 2016 https://github.com/nose-devs/nose/ Generally speaking nose is for python 2.x. I would recommend switch completely to pytest https://docs.nose2.io/en/latest/differences.html

================================================================================== ERRORS ==================================================================================
_____________________________________________________________ ERROR collecting tests/functional/test_smoke.py ______________________________________________________________
ImportError while importing test module '/home/tkloczko/rpmbuild/BUILD/boto3-1.18.23/tests/functional/test_smoke.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib64/python3.8/importlib/__init__.py:127: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
tests/functional/test_smoke.py:13: in <module>
    from nose.tools import assert_true
E   ModuleNotFoundError: No module named 'nose'
___________________________________________________________ ERROR collecting tests/functional/docs/test_smoke.py ___________________________________________________________
ImportError while importing test module '/home/tkloczko/rpmbuild/BUILD/boto3-1.18.23/tests/functional/docs/test_smoke.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib64/python3.8/importlib/__init__.py:127: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
tests/functional/docs/test_smoke.py:13: in <module>
    from nose.tools import assert_true
E   ModuleNotFoundError: No module named 'nose'
______________________________________________________ ERROR collecting tests/unit/resources/test_collection_smoke.py ______________________________________________________
ImportError while importing test module '/home/tkloczko/rpmbuild/BUILD/boto3-1.18.23/tests/unit/resources/test_collection_smoke.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib64/python3.8/importlib/__init__.py:127: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
tests/unit/resources/test_collection_smoke.py:15: in <module>
    from nose.tools import assert_false
E   ModuleNotFoundError: No module named 'nose'
========================================================================= short test summary info ==========================================================================
ERROR tests/functional/test_smoke.py
ERROR tests/functional/docs/test_smoke.py
ERROR tests/unit/resources/test_collection_smoke.py
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Interrupted: 3 errors during collection !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
============================================================================ 3 errors in 0.91s =============================================================================
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()'.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:7 (3 by maintainers)

github_iconTop GitHub Comments

2reactions
kdailycommented, Aug 18, 2021

Hi @kloczek,

Thanks. This is on our radar to switch completely to pytest. We’ll update here on the status of that work.

Related to https://github.com/boto/botocore/issues/2458 as well and will probably come out together.

1reaction
nateprewittcommented, Aug 28, 2021

Hi @kloczek, thanks for checking in. We actually did the work for this quite some time ago, and it’s currently on the pytest_migration branches in the respective repositories. The primary hold up is related to some requirements outside of these code bases in our release process. We’re currently working to get that unblocked and will provide updates when we’re ready to finalize the migration.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Basic usage — nose 1.3.7 documentation - Nosetests
Any python source file, directory or package that matches the testMatch regular expression (by default: (?:\b|_)[Tt]est will be collected as a test (or...
Read more >
Pneumonia (Ventilator-associated [VAP] and non ... - CDC
When determining whether to report multiple episodes of healthcare- associated pneumonia in a single patient, follow the Repeat Infection ...
Read more >
New Mexico Department of Information Technology: Home
Guiding and enhancing the use of geospatial technologies in state government. ... Our department offers services including Enterprise Application and ...
Read more >
Welcome to Python.org
The official home of the Python Programming Language.
Read more >
Python Nose Import Error - Stack Overflow
Also, to deal with the init package/module problem in a Django app, ... m3 to test some functions in n.py , you should...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found