From owner-freebsd-python@freebsd.org Sun Jun 10 03:08:32 2018 Return-Path: Delivered-To: freebsd-python@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 20FFC100C05E for ; Sun, 10 Jun 2018 03:08:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 9FAC0864DD for ; Sun, 10 Jun 2018 03:08:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 63ACE100C05C; Sun, 10 Jun 2018 03:08:31 +0000 (UTC) Delivered-To: python@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 50EA0100C05B for ; Sun, 10 Jun 2018 03:08:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DEBE7864DB for ; Sun, 10 Jun 2018 03:08:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 1DD9B17A57 for ; Sun, 10 Jun 2018 03:08:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w5A38T5R006380 for ; Sun, 10 Jun 2018 03:08:29 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w5A38THh006377 for python@FreeBSD.org; Sun, 10 Jun 2018 03:08:29 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 227862] devel/py-tox: update to 3.0.0 Date: Sun, 10 Jun 2018 03:08:30 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: koobs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jun 2018 03:08:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227862 --- Comment #5 from Kubilay Kocak --- (In reply to Kai from comment #4) testport -i is different to -I so may produce different results, but the te= st target for ports already installs build/run depends and has them installed = at that point, so theoretically the behaviour shouldn't be different. The issue with tox is that is creates a virtualenv that doesn't inherit from system site-packages by default, so those environments cant see the modules that were installed by ports (poudriere), and so tox tries to install them. I tried to make tox allow (enable) --sitepackages, but saw a different set = of test failures in that case, which is why I switched it back to using bare pytest (which is what tox calls anyway). Warnings, all else being equal, either imply dependencies in setup.py (*_requires) are incorrect/incomplete and need to be fixed, but in this cas= e i dont believe that's the cause. My current thought is that maybe since pluggy (etc) are *run time* dependencies, but building docs (with sphinx) is a *build* time activity, that's whats producing the warnings. That would imply pluggy (if it is inde= ed required to build docs), should be a setup_requires, at least conditionally= in the setup.py build docs target. However, I'm guessing its not actually required, but instead the warnings are an artifact of something else. --=20 You are receiving this mail because: You are on the CC list for the bug.=