From owner-freebsd-python@FreeBSD.ORG Sun Jan 26 14:45:02 2014 Return-Path: Delivered-To: freebsd-python@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 72E3276 for ; Sun, 26 Jan 2014 14:45:02 +0000 (UTC) Received: from forward2l.mail.yandex.net (forward2l.mail.yandex.net [84.201.143.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2805B1D2A for ; Sun, 26 Jan 2014 14:45:01 +0000 (UTC) Received: from smtp13.mail.yandex.net (smtp13.mail.yandex.net [95.108.130.68]) by forward2l.mail.yandex.net (Yandex) with ESMTP id AFC111AC0CA0 for ; Sun, 26 Jan 2014 18:44:58 +0400 (MSK) Received: from smtp13.mail.yandex.net (localhost [127.0.0.1]) by smtp13.mail.yandex.net (Yandex) with ESMTP id 7078BE400D0 for ; Sun, 26 Jan 2014 18:44:58 +0400 (MSK) Received: from unknown (unknown [178.76.234.16]) by smtp13.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id I5ha0i6xFz-ivJOGqD0; Sun, 26 Jan 2014 18:44:57 +0400 (using TLSv1 with cipher CAMELLIA256-SHA (256/256 bits)) (Client certificate not present) X-Yandex-Uniq: b6703758-2834-4f91-89ca-cc7850874f26 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1390747498; bh=uETz9FLpCjsPSaYSOKOAughMCAQPqjjnAgEb74q+iuo=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=eBneUEN868li8OeAHWv+c8yolekzD2wKe+RIUs3eEtymzuljLJNBOu14/AHarYIMv LhPep0B75luueGmWPZzoiii2TySL8FMg+pp2M37xvkgbfVo6JGJxJ0+SN2Zk4ojMDY 2qJoaU00Zkish1aOXUsA5bbkslBEClLOsTFnp/mM= Authentication-Results: smtp13.mail.yandex.net; dkim=pass header.i=@yandex.ru Message-ID: <52E51F5C.90804@yandex.ru> Date: Sun, 26 Jan 2014 18:44:44 +0400 From: Ruslan Makhmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-python@freebsd.org Subject: Re: PYDISTUTILS_AUTOPLIST question References: <52E4BCF4.3070507@yandex.ru> <20140126113022.GA1394@medusa.sysfault.org> <52E5007C.8060805@yandex.ru> <20140126142245.GB1394@medusa.sysfault.org> In-Reply-To: <20140126142245.GB1394@medusa.sysfault.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jan 2014 14:45:02 -0000 Marcus von Appen wrote on 26.01.2014 18:22: >> As we can see *.pyc/*.pyo pkg-plist entries were generated for >> pwreset_constructURL.py despite the fact that byte-compiling had failed. > > Thanks - I just checked, what exactly happens within the record magic for > those cases. distutils (and thus setuptools, since it does not do anything > special in that area) just picks up the .py files and adds entries for > matching .pyc and .pyo files without actually checking, if those files > could be compiled successfully. > The code snippet (distutils/install_lib.py, _bytecode_filenames()) actually > needs to verify, if .pyc/.pyo files exist, since the bytecode compiler > function (distutils/util.py, byte_compile() in indirect mode) > does not break on errors, but silently proceeds. > > Rather than adding a hack to bsd.python.mk to filter out such entries, I'd > like to see that issue fixed upstream: http://bugs.python.org/issue20397. > My current (quick'n'dirty) idea is to add a simple file existence verification > check into our currently supported versions. > > Cheers > Marcus Thank you for this. I though this is something under our control. Let's see what guys at python.org say. -- Regards, Ruslan T.O.S. Of Reality