-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
doctest marks readme files without doctests as skipped. #1578
Labels
good first issue
easy issue that is friendly to new contributor
status: help wanted
developers would like help from experts on this topic
type: bug
problem that needs to be addressed
Comments
RonnyPfannschmidt
added
type: bug
problem that needs to be addressed
status: help wanted
developers would like help from experts on this topic
good first issue
easy issue that is friendly to new contributor
labels
Jun 1, 2016
i think this is related to the stdlib doctest limits, i'm not sure how easy a fix is, i hope someone else will take a look |
found the issue working on a fix now |
it's a ∀ x: P(x) ↛ ∃ x: P(x) issue |
can you explain that for a non-mathematican? |
All does not imply exists |
graingert
added a commit
to graingert/pytest
that referenced
this issue
Jun 1, 2016
graingert
added a commit
to graingert/pytest
that referenced
this issue
Jun 1, 2016
graingert
added a commit
to graingert/pytest
that referenced
this issue
Jun 1, 2016
graingert
added a commit
to graingert/pytest
that referenced
this issue
Jun 1, 2016
graingert
added a commit
to graingert/pytest
that referenced
this issue
Jun 1, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
good first issue
easy issue that is friendly to new contributor
status: help wanted
developers would like help from experts on this topic
type: bug
problem that needs to be addressed
Here's the issue, https://travis-ci.org/graingert/dockhand/jobs/134400724#L202
on these files: https://github.com/graingert/dockhand/tree/69be7c180e67407aca462b899ff1259b3e09f080
The text was updated successfully, but these errors were encountered: