Python byte-compilation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I wonder if anyone has a solution to incorrect path-names in
byte-compiled python packages.

In the normal dist-utils install step within the context of an rpmbuild,
all paths get prepended
/var/tmp/buildroot-.../usr/lib/python2.x/site-packages.  This causes
incorrect stack trace information to be shown.

I'd taken to doing byte-compilation in the %post step to fix this, but
I've discovered a much worse effect from this in that all the .pyc and
pyo files thus fall outside RPM control, and when removing the package,
stay in place, effectively negating the removal (although the
translation units are definitely gone...)

Any thoughts?

Alan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFDPoxdCfroLk4EZpkRAr+FAKCyb/b+q8MRn5Nf5X+x0HUCi6sHBgCcDduj
dhvYknEVuoW7ziQBTEieuKw=
=Dlu+
-----END PGP SIGNATURE-----

--
Fedora-packaging mailing list
Fedora-packaging@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-packaging

[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Forum]     [KDE Users]

  Powered by Linux