Running pytest

[galund]

When running pytest, I got

ImportError while importing test module '/Users/george.lund/dev/md2cf/tests/unit/test_document.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
../../.pyenv/versions/3.10.4/lib/python3.10/importlib/__init__.py:126: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
tests/unit/test_document.py:4: in <module>
    from tests.utils import FakePage
E   ModuleNotFoundError: No module named 'tests'

So I had to add

pythonpath = .

to pytest.ini.

I assume this isn't expected, are there some docs I should read? ta

[galund]

I note that this is also affecting automated builds eg https://github.com/iamjackg/md2cf/actions/runs/5053801589/jobs/9068013126

There seems to be a change in what's happening to sys.path after a pip install --editable, between version 23.0 of pip and version 23.1

We can potentially fix this by pinning the version of pip, but it'd be nice to figure out if this is a bug in pip or something that can be fixed here...

[galund]

I've reported this as a bug in pip - pypa/pip#12094

I'm going to create a PR here to pin the version of pip that md2cf uses to the last working version, pending getting a better understanding of whether some change will be required long-term to allow us to upgrade.

[galund]

I changed my mind - how would a developer know to use a specific version of pip, even if we fixed the CI? Instead, see #93