FS#41438 - [mutagen] package includes compiled bytecode in /usr/bin

Attached to Project: Arch Linux
Opened by Wieland Hoffmann (Mineo) - Friday, 01 August 2014, 20:22 GMT
Last edited by Eric Belanger (Snowman) - Friday, 29 August 2014, 02:44 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Eric Belanger (Snowman)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
All the files in the mutagen package in /usr/bin that end with the letter c are compiled versions of the files without the c. They were created by the test runner, but don't need to be shipped in a package.

The upstream ticket is https://bitbucket.org/lazka/mutagen/issue/179/running-the-tests-leaves-compiled-bytecode

(The 'install -m755 tools/* "${pkgdir}/usr/bin"' line in the PKGBUILD is no longer necessary as well, setup.py automatically installs the scripts)

Additional info:
* package version(s) 1.23
This task depends upon

Closed by  Eric Belanger (Snowman)
Friday, 29 August 2014, 02:44 GMT
Reason for closing:  Fixed
Additional comments about closing:  mutagen-1.24-1
Comment by Doug Newgard (Scimmia) - Friday, 01 August 2014, 21:27 GMT
Shipping the byte compiled code makes it load faster, why would you want it removed?

Edit: ah, these are just c added to the filename, not .pyc files. Different than what I was thinking.
Comment by Wieland Hoffmann (Mineo) - Saturday, 02 August 2014, 08:54 GMT
I'm not arguing against shipping byte code for python libraries in general, I'm only arguing against shipping byte code in /usr/bin because it makes every application show up twice in the shell completion - annoying. Mutagens files are also small enough that the speedup gained by shipping them precompiled is probably negligible.
Comment by Wieland Hoffmann (Mineo) - Tuesday, 26 August 2014, 16:13 GMT
FWIW, upstream has applied a patch to fix this.

Loading...