-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Merge from master to features #1705
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
Merge from master to features #1705
Conversation
…funcargvalue issue1625, rename getfuncargvalue to getfixturevalue
…lapse_false Fixes pytest-dev#1503 no longer collapse false explanations
I have came across this when noticing that universal-ctags fails to parse this correctly (universal-ctags/ctags#997).
This was added in b2d66b9 but is a bad idea. When a plugin can't be imported, commandline options (optionally set in pytest.ini) could be undefined, which means pytest bails out much earlier before showing the warning, which is hard to debug. Fixes pytest-dev#1479, also see pytest-dev#1307 and pytest-dev#1497
Combining multiple imports the "import pdb" imports the pytest module as opposed to the python debugger.
Don't ignore ImportError when importing setuptools plugins
Update website wrt indiegogo campaign
…epr__ Simplify Argument.__repr__
Add changelog entry for pytest-dev#1564
Rename the default plugin "pdb" into "debugging"
Even though catch is a Python keyword, 'catched' just looks terrible in text. If the text was supposed to reference the keyword, then 'catched' should be changed to "'catch'ed".
catched -> caught
I wouldn't have even attempted what I did to cause pytest-dev#1688 if this had been there.
Document the interaction of autouse scopes
Add changelog to requirements for pytest-dev plugins
Some of our builds have been timing out (over 1 hour), on AppVeyor
Split AppVeyor test runs in multiple jobs to avoid timeout issues
…-docs Fix links and removed 404 links from talks.rst
@@ -187,6 +210,9 @@ | |||
.. _@Vogtinator: https://github.com/Vogtinator | |||
.. _@blueyed: https://github.com/blueyed | |||
.. _@fengxx: https://github.com/fengxx | |||
.. _@bagerard: https://github.com/bagerard | |||
.. _@davehunt: https://github.com/davehunt |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
INFO CHANGELOG.rst:242 Duplicate explicit target name: "@davehunt".
(he's already on line 216/242)
Hmm it failed on Windows:
The first error ( |
at second glance it seems like a hypothesis bug @DRMacIver might know more |
So can we merge this anyway? But every single PR will show this issue? How wise is it to make all PRs dependent on an external project? |
To be honest I'd rather wait a day or two to see what @DRMacIver has to say about it - and if it really turns out to be a hypothesis issue and we don't find a quick fix, just blacklist the hypothesis tests for now, merge this, and then investigate afterwards.
Do you mean in general, or if we'd merge this? |
This merge is long overdue now, so I would rather do it now rather than wait a few more days. I propose we report the issue to hypothesis repository and xdist = request.config.pluginmanager.getplugin('xdist')
if xdist:
pytest.xfail(reason='bad interaction with xdist, waiting on HypothesisWorks/hypothesis-python/#X ')
All PRs already depend on a bunch of external projects: |
@nicoddemus It is a collection error though, maybe we should be adding Sure about the external dep, it's unavoidable I guess. It's just a bit annoying that this seemingly unrelated thing is holding up what should be a routine merge. |
It happens at collection time because the |
Oh! According to HypothesisWorks/hypothesis#344 a fix is out in Hypothesis 3.4.1 (this is why I suggested waiting, @DRMacIver is incredibly quick with fixing bugs 😆). Since we don't seem to pin test dependency versions, rerunning the build now. |
Oh I didn't know that, otherwise I might have suggested the same! 😁 Thanks @DRMacIver! |
I'm hitting that "Merge" button the second I see that AppVeyor build green! 😆 |
Thanks everyone! 👍 |
Hmm. It's interesting that it errors there though. It's supposed to defer as much as possible to test execution time to speed up file loading and localize errors better. |
new pr