FS#27688 - namcap doesn't think .pyo files are architecture dependent.
Attached to Project:
Arch Linux
Opened by Peter Lewis (petelewis) - Friday, 23 December 2011, 18:30 GMT
Last edited by Allan McRae (Allan) - Saturday, 24 December 2011, 00:38 GMT
Opened by Peter Lewis (petelewis) - Friday, 23 December 2011, 18:30 GMT
Last edited by Allan McRae (Allan) - Saturday, 24 December 2011, 00:38 GMT
|
Details
Description:
Sometimes, namcap warns that a package should have architecture "any", when it contains compiled python (.pyo) files. But, .pyo files are architecture dependent. This doesn't seem to happen on all such packages. According to [1], .pyo files are architecture dependent. [1] http://bytes.com/topic/python/answers/25152-pyc-pyo-architecture-independent Additional info: * package version(s) 3.2.1 Steps to reproduce: Download and build this package: https://aur.archlinux.org/packages.php?ID=21531 Run namcap on the built package. I get: python-mpd-git W: No ELF files and not an "any" package python-mpd-git W: Dependency included and not needed ('python2') Weirdly, this doesn't happen on every such package. For example, running namcap on python2-urwid-1.0.1-1-x86_64.pkg.tar.xz doesn't give the warning. (Or is it being cleverer than I am and only some .pyo files are in fact architecture dependent?) |
This task depends upon
Comment by Allan McRae (Allan) -
Friday, 23 December 2011, 22:12 GMT
Comment by Peter Lewis (petelewis) -
Saturday, 24 December 2011, 00:33 GMT
From [1], I get the impression that they are architecture
independent, which in fact they are... There are incompatibilites
between the files generated by different python versions.
Lol, yeah sorry for the noise. I seem to be getting quite good at
reading something and taking the exact opposite meaning from it.