Date: Sun, 26 Jan 2014 18:44:44 +0400 From: Ruslan Makhmatkhanov <cvs-src@yandex.ru> To: freebsd-python@freebsd.org Subject: Re: PYDISTUTILS_AUTOPLIST question Message-ID: <52E51F5C.90804@yandex.ru> In-Reply-To: <20140126142245.GB1394@medusa.sysfault.org> References: <52E4BCF4.3070507@yandex.ru> <20140126113022.GA1394@medusa.sysfault.org> <52E5007C.8060805@yandex.ru> <20140126142245.GB1394@medusa.sysfault.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52E51F5C.90804>