|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
ignatenkobrain commented 5 years ago | ||
churchyard commented 5 years ago Explicit is better than implicit. Also, either this or a comment that says: Need to do py2_install first, so the py3_install overrides the files... - if you ar enot strongly against this, I'd rather keep it. | ||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
ignatenkobrain commented 5 years ago I've heard that some upstreams use cythonize3... Not sure if we want to keep compatibility. | ||
churchyard commented 5 years ago Let's remove it now and if unpatched upstream packages will FTBFS, i'll add a compatibility symblink. | ||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
Only have one /usr/bin/cython
.
According to the current packaging guidelines, if the functionality of the executable is the same regardless of the Python version, the executable should be shipped by Python 3 package only.
This is the case for Cython.
Also, don't disable tests everywhere when they should only fail on Big Endian (they fail on all arches).
no need for this, $py3_install should overwrite those binaries.