[arch-dev-public] Improving the package guidelines

Felix Yan felixonmars at archlinux.org
Thu Jun 28 21:59:04 UTC 2018

On 06/29/2018 05:06 AM, Eli Schwartz via arch-dev-public wrote:
> Also I'd like to discuss what seems to me a common misconception in
> python packaging -- specifically, the use of cp -r source source-py2 and
> building both separately.
> Best I can tell, this is primarily motivated by fear of py2/py3 specific
> bytecode being generated, but the thing is, this bytecode is all
> generated during package() inside of "$pkgdir" during the install step.
> You can check the contents of the build/ directory... it just copies the
> .py files and builds any ext_modules.

The main reason behind this (or why I started doing this) was sometimes
the tests run inside the sources tree made both versions' .pyc files
into the tree itself, and finally end up in the package. I had this
problem for several times and end up having the separated build
directories as template for new packages.

This seems not the case for most packages now, so I agree that it should
be avoided.

Felix Yan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.archlinux.org/pipermail/arch-dev-public/attachments/20180629/26154740/attachment.asc>

More information about the arch-dev-public mailing list