From 338e171e7008a8e3fdc2d7677de96b3b2da9e430 Mon Sep 17 00:00:00 2001 From: Marek Szuba Date: Fri, 12 Mar 2021 12:21:43 +0000 Subject: [PATCH] dev-python/ruamel-yaml: update note in pypy3_collection_deprecation.patch The test in question fails to produce a deprecation warning even under pypy3.7, meaning we do not in fact implicitly assume the Gentoo pypy3 target to be 3.6. Signed-off-by: Marek Szuba --- .../ruamel-yaml-0.16.13-pypy3_collection_deprecation.patch | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/dev-python/ruamel-yaml/files/ruamel-yaml-0.16.13-pypy3_collection_deprecation.patch b/dev-python/ruamel-yaml/files/ruamel-yaml-0.16.13-pypy3_collection_deprecation.patch index 9f7be2676ec81..15d00625b68e3 100644 --- a/dev-python/ruamel-yaml/files/ruamel-yaml-0.16.13-pypy3_collection_deprecation.patch +++ b/dev-python/ruamel-yaml/files/ruamel-yaml-0.16.13-pypy3_collection_deprecation.patch @@ -1,8 +1,5 @@ -Note that this implicitly assumes pypy3 to be compatible with CPython 3.6. -The test could in principle be more robust - but between 3.7 support -in PyPy is still being alpha-grade and the fact there will be many more -serious issues with switching the Gentoo pypy3 target to those versions, -why bother for now. +This does not produce a deprecation warning under PyPy, even pypy3.7 +(last tested on 2021-03-12 using version 7.3.3-beta0). --- a/_test/test_deprecation.py +++ b/_test/test_deprecation.py