From owner-freebsd-python@FreeBSD.ORG Sun Jul 6 19:56:16 2014 Return-Path: <owner-freebsd-python@FreeBSD.ORG> Delivered-To: python@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CB99BA42; Sun, 6 Jul 2014 19:56:16 +0000 (UTC) Received: from fire.magemana.nl (magemana.nl [IPv6:2a01:7c8:aaae:25e::1]) by mx1.freebsd.org (Postfix) with ESMTP id 950192FCE; Sun, 6 Jul 2014 19:56:16 +0000 (UTC) Received: by fire.magemana.nl (Postfix, from userid 1003) id 187E24AB4C4; Sun, 6 Jul 2014 21:56:09 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by fire.magemana.nl (Postfix) with ESMTP id 13A9C4AB4B6; Sun, 6 Jul 2014 21:56:09 +0200 (CEST) Date: Sun, 6 Jul 2014 21:56:09 +0200 (CEST) From: Melvyn Sopacua <melvyn@magemana.nl> To: ports@FreeBSD.org Subject: Ports that don't actually support Python 3.x Message-ID: <alpine.BSF.2.00.1407062139390.2458@fire.magemana.nl> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Cc: python@FreeBSD.org X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: FreeBSD-specific Python issues <freebsd-python.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-python>, <mailto:freebsd-python-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-python/> List-Post: <mailto:freebsd-python@freebsd.org> List-Help: <mailto:freebsd-python-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-python>, <mailto:freebsd-python-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sun, 06 Jul 2014 19:56:16 -0000 Hello, I'm coming accross a few ports that are in the tree as we speak, that do not actually install correctly with Python 3.x but aren't marked as 2.7 only. There seems to be 2 cases: 1. incompatibility in setup.py or related, thus failing in configure 2. incompatibility in the code itself, thus failing in byte_compile The ones in 2 fail with PYDISTUTILS_AUTOPLIST in install, because the files cannot be compiled and thus are missing when using the plist. I've got a few in PRs, few in the queue to become PR's, but perhaps a broader effort is needed? I'm willing to help, if an exp-run or something similar would generate a list. PS: A common error is: `except Exception, var:`. This can probably be fixed with a REINPLACE_CMD that can be standardized, but so far, bringing the port up-to-date with upstream fixes the problem (notable exception being www/py-beautifulsoup32). -- Melvyn