From owner-freebsd-python@freebsd.org Sat Jun 9 10:22:19 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 AF1621011651 for ; Sat, 9 Jun 2018 10:22:19 +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 4568573775 for ; Sat, 9 Jun 2018 10:22:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id F324B1011648; Sat, 9 Jun 2018 10:22:18 +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 E181A1011647 for ; Sat, 9 Jun 2018 10:22:18 +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 8189F7376E for ; Sat, 9 Jun 2018 10:22:18 +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 CDE95F63C for ; Sat, 9 Jun 2018 10:22:17 +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 w59AMHFr070825 for ; Sat, 9 Jun 2018 10:22:17 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w59AMH7d070824 for python@FreeBSD.org; Sat, 9 Jun 2018 10:22:17 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: Sat, 09 Jun 2018 10:22:18 +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: freebsd_ports@k-worx.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: Sat, 09 Jun 2018 10:22:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227862 --- Comment #4 from Kai --- (In reply to Kubilay Kocak from comment #3) Hello Kubilay, thanks for committing the update. I'll rework a small rebased patch for the DOCS option but I'm a little confused about the fact that there were some b= uild errors with the DOCS option enabled. Maybe I'm still missing some QA testing technique and thus my workflow needs some improvement? My usual way to do QA with the "make test" target for Pyt= hon ports is at the moment: Testing the build process: > poudriere testport -i -j JAIL -p PORTS -o PORT_TO_TEST Inside the jail I do usually for Python ports (using py-tox as example with FLAVOR=3Dpy27) with a already defined "do-test" target: > cd /usr/ports/devel/py-tox > make test After these steps I check the logs for packages, that were missing or have = been fetched from PyPi. You're right that both devel/py-pluggy + devel/py-py packages are not requi= red as DOCS_BUILD_DEPENDS to build the package successfully. But there will be = some warnings during the sphinx build process that these modules could not be imported when they are left out, e.g: > ImportError: No module named pluggy > /wrkdirs/usr/ports/devel/py-tox/work-py27/tox-3.0.0/doc/plugins.rst:89: >= WARNING: autodoc: failed to import class u'TestenvConfig' from module u'to= x.config'; the following exception was raised: Can such warnings be safely ignored? --=20 You are receiving this mail because: You are on the CC list for the bug.=