-
Notifications
You must be signed in to change notification settings - Fork 443
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
make test-types
fails for plugins when tutor is installed in editable mode
#956
Comments
Looking into it |
Here's a Dockerfile to reproduce the issue:
Building the image succeeds when we replace |
See this issue in practice in this failed test run: https://github.com/overhangio/tutor-credentials/actions/runs/7568050350/job/20608428713 |
The strict mode also seems to does the trick. It can be acheived through: |
@regisb Can you please provide insights on it? If there is no more discussion on it, we can close this. |
This issue is still open. For instance, consider the case of nightly. We are telling people to install tutor with |
This is an attempt both to modernize the packaging and to fix mypy testing in editable mode (issue #956). Packaging seems to work, but mypy testing still fails. Will now attempt to migrate from setuptools to hatch for building.
This is an attempt both to modernize the packaging and to fix mypy testing in editable mode (issue #956). Packaging seems to work, but mypy testing still fails. Will now attempt to migrate from setuptools to hatch for building.
Bug description
Type tests fail when tutor is installed in editable mode. This is inconvenient when testing plugins locally.
How to reproduce
Install tutor in editable mode:
Run type tests for a plugin:
That error is caused by the fact that mypy does not find the tutor module, has the following attests:
Additional context
This is a known issue. See the upstream tickets in mypy and setuptools:
python/mypy#13392
pypa/setuptools#3518
The issue can be bypassed by installing tutor in legacy mode:
Or by installing in non-editable mode:
The text was updated successfully, but these errors were encountered: