-
-
Notifications
You must be signed in to change notification settings - Fork 514
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
sage -pytest #33572
Comments
Branch: u/mkoeppe/sage__pytest |
comment:2
Here's an attempt at this command, but I think I'll need some help here to make it actually work:
New commits:
|
Changed author from Matthias Koeppe to Matthias Koeppe, ... |
Commit: |
comment:3
That looks like a typical cyclic import that relies on
|
comment:4
Moreover, there are a few dozens of such import errors:
|
comment:5
Can't you just add |
comment:6
There is already a hook which adds |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Changed author from Matthias Koeppe, ... to Matthias Koeppe |
comment:9
Ah that's what you had in mind. Seems to work indeed. Can you please add a comment that prevents pyright to complain about the unused import and add a link to #33580. Thanks! |
comment:12
should probably fallback to |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:23
Replying to @tobiasdiez:
This file is to be considered a data file; it's not a module of the Sage library |
comment:24
Thanks for the follow-up. However, during the merge something seems to went wrong. The collect_ignore in the test config shouldn't be readded. |
comment:25
Replying to @mkoeppe:
So you are saying it should be removed during collection? Then please do so by adding a filter in pytest_collect_file similar to #33560. |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
comment:27
Indeed. Thanks for catching the mistake in rebasing |
comment:28
Replying to @tobiasdiez:
The directories marked by the presence of a
Not sure if we want to use this mechanism somehow or just hardcode it in |
comment:30
Replying to @mkoeppe:
I would say its simpler to exclude these two directories in conftest. As you already know, I'm not a big fan of such marker files in general. |
comment:31
OK, sounds good. |
comment:32
Given that |
comment:33
Why not? |
comment:34
Not the same because there is no existing practice of running pytest on that file. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:37
There is very much existing practice of running |
comment:38
Let's get this in please |
comment:39
Okay. I still think these folders with |
comment:40
Thanks! |
Changed branch from u/mkoeppe/sage__pytest to |
Thin wrapper around
pytest
for running it in the Sage environment.as suggested in #31924 comment:94
Similar to our existing wrapper
sage -tox
.CC: @tornaria @tobiasdiez @soehms
Component: doctest framework
Author: Matthias Koeppe
Branch/Commit:
8825079
Reviewer: Tobias Diez
Issue created by migration from https://trac.sagemath.org/ticket/33572
The text was updated successfully, but these errors were encountered: