Date: Wed, 13 Jun 2018 18:27:11 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 227862] devel/py-tox: update to 3.0.0 Message-ID: <bug-227862-21822-Fno5OyX8QK@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-227862-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-227862-21822@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227862 Kai <freebsd_ports@k-worx.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #194231| |maintainer-approval?(koobs@ Flags| |FreeBSD.org) --- Comment #6 from Kai <freebsd_ports@k-worx.org> --- Created attachment 194231 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=194231&action=edit py-tox-3.0.0-DOCS.patch (In reply to Kubilay Kocak from comment #5) Thank you for the detailed explanations and insights. I really appreciate that. Attached is a rebased patch with the DOCS option. The builds are fine so far and with the DOCS option enabled, there are 7 warnings (related to devel/py-pluggy + devel/py-py) during the build.l The test results are: With Python 2.7: > 368 passed, 4 skipped, 1 xfailed (due a bug as noted in the results) in 45.71 seconds With Python 3.6: > 369 passed, 3 skipped, 1 xfailed (due a bug as noted in the result) in 57.34 seconds If the problems with the packages "packaging" and "simple" still persist in some way it would be no problem for me to leave the port at its current state without the DOCS option. (Although it's always quite handy to have some reference if you're travelling or your ISP let you down.) -- You are receiving this mail because: You are on the CC list for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-227862-21822-Fno5OyX8QK>