On Fri, 17 Feb 2017, Stephan Kulow wrote:
Am 17.02.2017 um 11:12 schrieb Richard Biener:
From looking at package rebuilds I do remember seeing changing python triggering all -python packages to be rebuilt (when ideally when just shipping .py files no build would be involved).
Why would we prefer every user compiling over us building once? If the pyc files are not compatible with all python versions, we need to have a require on the python abi - so we know when to rebuild.
Sure. Just as was mentioned if we ship .pyc why do we ship .py files? Eventually it's about choice but then we can as well split packages into python-X-py and python-X-pyc both providing python-X (or some other way). The incompatibility thing was just something I remember from the past, it may be no longer true (python may just silently fall back to reading the .py file if the .pyc is incompatible). Richard.
Greetings, Stephan
-- Richard Biener <rguenther@suse.de> SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org