From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] test/py: Fix pytest4 deprecation warnings
Date: Wed, 13 Mar 2019 12:27:38 +0100 [thread overview]
Message-ID: <904b8981-a18c-db82-e8bc-e75ea898f2e9@gmail.com> (raw)
In-Reply-To: <20190313112501.GB8732@bill-the-cat>
On 3/13/19 12:25 PM, Tom Rini wrote:
> On Wed, Mar 13, 2019 at 12:20:49PM +0100, Marek Vasut wrote:
>> On 3/13/19 12:19 PM, Tom Rini wrote:
>>> On Wed, Mar 13, 2019 at 05:08:14AM +0100, Marek Vasut wrote:
>>>
>>>> Fix the following spit from pytest:
>>>>
>>>> u-boot/test/py/conftest.py:438: RemovedInPytest4Warning: MarkInfo objects are deprecated as they contain merged marks which are hard to deal with correctly.
>>>> Please use node.get_closest_marker(name) or node.iter_markers(name).
>>>> Docs: https://docs.pytest.org/en/latest/mark.html#updating-code
>>>> for board in mark.args:
>>>>
>>>> In both cases, the later suggestion is applicable.
>>>>
>>>> Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com>
>>>> Cc: Igor Opaniuk <igor.opaniuk@linaro.org>
>>>> Cc: Tom Rini <trini@konsulko.com>
>>>> Cc: Simon Glass <sjg@chromium.org>
>>>
>>> Deferred, for now we don't support newer pytest than 2.8.7 and you'll
>>> need to use virtualenv to set that up if needed. There is not, AFAICT,
>>> a way to support both versions.
>>
>> That's what's in debian testing though, so maybe we need to support it
>> somehow.
>
> Yes, I'm _very_ frustrated at the speed at which pytest went from "this
> is the API" to "this API is deprecated" to "this API doesn't work and
> here's the new, incompatible API". Debian/testing needs to use
> virtualenv to setup a python area with older pytest installed, just like
> we do in .travis.yml.
Can't we rather have people use the new APIs and virtualenv new python?
> And wrt making our python stuff happier with newer versions, I'm far
> more worried about all of the python2-and-not-3 scripts we have
> currently. :(
Right
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2019-03-13 11:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 4:08 [U-Boot] [PATCH] test/py: Fix pytest4 deprecation warnings Marek Vasut
2019-03-13 11:19 ` Tom Rini
2019-03-13 11:20 ` Marek Vasut
2019-03-13 11:25 ` Tom Rini
2019-03-13 11:27 ` Marek Vasut [this message]
2019-03-13 11:29 ` Tom Rini
2019-03-13 11:30 ` Marek Vasut
2019-03-13 16:01 ` Tom Rini
2019-03-13 18:23 ` Marek Vasut
2019-03-13 19:42 ` Tom Rini
2019-03-14 0:20 ` Marek Vasut
2019-03-14 1:01 ` Tom Rini
2019-03-15 17:39 ` Marek Vasut
2019-03-16 1:50 ` Tom Rini
2019-03-16 20:23 ` Marek Vasut
2019-03-16 20:35 ` Tom Rini
2019-03-17 12:47 ` Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=904b8981-a18c-db82-e8bc-e75ea898f2e9@gmail.com \
--to=marek.vasut@gmail.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox