You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# From project root directory (location of pyproject.toml)
$ coverage run foo.py
$ coverage combine
Traceback (most recent call last):
File "/path/to/venv/bin/coverage", line 8, in<module>sys.exit(main())
~~~~^^
File "/path/to/venv/lib/python3.13/site-packages/coverage/cmdline.py", line 970, in main
status = CoverageScript().command_line(argv)
File "/path/to/venv/lib/python3.13/site-packages/coverage/cmdline.py", line 681, in command_line
return self.do_run(options, args)
~~~~~~~~~~~^^^^^^^^^^^^^^^
File "/path/to/venv/lib/python3.13/site-packages/coverage/cmdline.py", line 855, in do_run
self.coverage.start()
~~~~~~~~~~~~~~~~~~~^^
File "/path/to/venv/lib/python3.13/site-packages/coverage/control.py", line 660, in start
self._init()
~~~~~~~~~~^^
File "/path/to/venv/lib/python3.13/site-packages/coverage/control.py", line 365, in _init
self._plugins.load_from_config(self.config.plugins, self.config)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/path/to/venv/lib/python3.13/site-packages/coverage/plugin_support.py", line 48, in load_from_config
__import__(module)
~~~~~~~~~~^^^^^^^^
ModuleNotFoundError: No module named 'my_local_plugin'
To Reproduce
How can we reproduce the problem? Please be specific. Don't link to a failing CI job. Answer the questions below:
What version of Python are you using? 3.13
What version of coverage.py shows the problem? The output of coverage debug sys is helpful.
Expected behavior coverage should be able to import the package, using the current working directory. Setting PYTHONPATH=$(pwd) then of course it works.
The text was updated successfully, but these errors were encountered:
Describe the bug
Consider a project:
And then
To Reproduce
How can we reproduce the problem? Please be specific. Don't link to a failing CI job. Answer the questions below:
coverage debug sys
is helpful.Expected behavior
coverage
should be able to import the package, using the current working directory. SettingPYTHONPATH=$(pwd)
then of course it works.The text was updated successfully, but these errors were encountered: