Conversation
We should replace the wiki document to a link to this document now
…p-docs Add Deprecation Roadmap to backward compatibility document
Fix assertion rewrite to match module names correctly
…scription Handle marks without description
|
Don't have time for a closer look right now, but I got some errors: With Then After removing that and commenting out some code I have which ties into pytest-catchlog, things seem to run fine so far. Will report back when it's done. Version info: |
|
Thanks @The-Compiler!
I will go ahead and implement those two solutions and upload a new package. |
|
Hmm, I also get failing tests in this file, which uses pytester to run pytest with coverage and then checks the |
|
Bisected to 333a9ad which de-vendors pluggy. I guess that also came with some kind of update to the pluggy being used? |
Which file? |
Actually on second thought, I'm reverting the change that deprecated |
|
I opened #2946 for the |
We eventually want to replace py.io.TerminalWriter (exposed as "_tw" in TerminalReporter) by something else, so deprecating access to "_tw" and making it public as "writer" is contrary to that.
Trying to install pytest-3.3 and pytest-catchlog will result in an option conflicts because both declare the same options.
|
|
Updated pin to include |
|
🏍 |
CHANGELOG.rst
Outdated
| <https://github.com/pytest-dev/pytest/issues/2767>`_) | ||
|
|
||
| - Pytest no longer supports Python **2.6** and **3.3**. Those Python versions | ||
| are EOL for some time now and incurr maintanance and compatibility costs on |
There was a problem hiding this comment.
Typo maintanance should be maintenance.
CHANGELOG.rst
Outdated
| previous output style can be set by setting the new ``console_output_style`` | ||
| to ``classic``. (`#2657 <https://github.com/pytest-dev/pytest/issues/2657>`_) | ||
|
|
||
| - Match ``warns`` signature to ``raises`` by adding ``match`` keyworkd. (`#2708 |
| - Pytest now captures and displays output from the standard `logging` module. | ||
| The user can control the logging level to be captured by specifying options | ||
| in ``pytest.ini``, the command line and also during individual tests using | ||
| markers. Also, a ``caplog`` fixture is available that enables users to test |
CHANGELOG.rst
Outdated
| - Refactored internal Python 2/3 compatibility code to use ``six``. (`#2642 | ||
| <https://github.com/pytest-dev/pytest/issues/2642>`_) | ||
|
|
||
| - Stop vendoring ``pluggy`` - we're missing out on it's latest changes for not |
There was a problem hiding this comment.
Heh looks like a typo on my part: should be its.
There was a problem hiding this comment.
yikes - based on the number of minor easy to miss typos, we should investigate better news file auto scanning - else we run into them all at once at release time
There was a problem hiding this comment.
Or actually start reviewing changelog entries 😉
|
Fixed all typos, thanks @tgoodlet! |
The-Compiler
left a comment
There was a problem hiding this comment.
Some comments on the changelog - it runs the qutebrowser testsuite fine now!
CHANGELOG.rst
Outdated
| ------------------------- | ||
|
|
||
| - Pytest no longer supports Python **2.6** and **3.3**. Those Python versions | ||
| are EOL for some time now and incurr maintenance and compatibility costs on |
| Deprecations and Removals | ||
| ------------------------- | ||
|
|
||
| - Pytest no longer supports Python **2.6** and **3.3**. Those Python versions |
There was a problem hiding this comment.
Hm, this sounds like this release really should be 4.0 instead...
There was a problem hiding this comment.
Perhaps, but we decided at the time to just increase a minor version instead.
Either way I think it might be too late to change that decision now TBH.
There was a problem hiding this comment.
Fair point - I missed the original decision. Let's see how that goes...
CHANGELOG.rst
Outdated
| ``CallSpec2`` class. (`#2672 | ||
| <https://github.com/pytest-dev/pytest/issues/2672>`_) | ||
|
|
||
| - remove ParameterSet.deprecated_arg_dict - its not a public api and the lack |
There was a problem hiding this comment.
remove -> Remove for consistency.
CHANGELOG.rst
Outdated
|
|
||
| - Replace the old introspection code in compat.py that determines the available | ||
| arguments of fixtures with inspect.signature on Python 3 and | ||
| funcsigs.signature on Python 2. This should respect __signature__ |
There was a problem hiding this comment.
Might want to add `` around __signature__.
CHANGELOG.rst
Outdated
| declarations on functions. (`#2267 | ||
| <https://github.com/pytest-dev/pytest/issues/2267>`_) | ||
|
|
||
| - Report only once tests with global ``pytestmark`` variable. (`#2549 |
There was a problem hiding this comment.
Report tests with ... only once.
CHANGELOG.rst
Outdated
| <https://github.com/pytest-dev/pytest/issues/2549>`_) | ||
|
|
||
| - Now pytest displays the total progress percentage while running tests. The | ||
| previous output style can be set by setting the new ``console_output_style`` |
There was a problem hiding this comment.
the new ... -> the new ... setting?
CHANGELOG.rst
Outdated
| ``err`` can be accessed by attribute. (`#2879 | ||
| <https://github.com/pytest-dev/pytest/issues/2879>`_) | ||
|
|
||
| - Add ``capfdbinary`` a version of ``capfd`` which returns bytes from |
| ``readouterr()``. (`#2923 | ||
| <https://github.com/pytest-dev/pytest/issues/2923>`_) | ||
|
|
||
| - Add ``capsysbinary`` a version of ``capsys`` which returns bytes from |
CHANGELOG.rst
Outdated
| ``readouterr()``. (`#2934 | ||
| <https://github.com/pytest-dev/pytest/issues/2934>`_) | ||
|
|
||
| - Implement feature to skip ``setup.py`` files when ran with |
|
|
||
| Deprecated in ``3.0``. | ||
|
|
||
| Past Releases |
There was a problem hiding this comment.
Dropping legacy Python support should at least be mentioned here.
|
@The-Compiler thanks for the review, fixed the typos/wording you mentioned. 👍 Just in case you didn't know, you can edit files directly in GH's web interface to fix typos and such, committing directly into my branch. 😉 |
|
Hm, I indeed didn't think about that! It never worked when trying to clone a PR repo and push there for whatever reason, but I guess the web editor is fine for simple things like this. |
|
|
||
| - Remove internal ``_preloadplugins()`` function. This removal is part of the | ||
| ``pytest_namespace()`` hook deprecation. (`#2236 | ||
| <https://github.com/pytest-dev/pytest/issues/2236>`_) |
There was a problem hiding this comment.
This link is wrong, it should be #2636 if I'm not mistaken...
There was a problem hiding this comment.
@uSpike it doesn't really matter, GH automatically redirects it to the appropriate page. 😉
All of our links use the pytest/issues/# form, even if the number actually points to a PR.
There was a problem hiding this comment.
I'm confused because if I go to #2236 it's a PR about junitxml, "Change junitxml.py to produce results that comply with Junitxml schema"
There was a problem hiding this comment.
@uSpike OH you are right, sorry I misinterpreted what you said.
I will fix this on master after the release, the package has just now finished testing and I would not like to go over the entire process again. 😁
No description provided.