jan matejek-4 wrote
On 21.3.2017 10:15, Luigi Baldoni wrote:
I'm still having problems with nosetests, that is I'm seeing encoding errors in 2.x when the original python 2 package didn't have any (while the python3 one did).
Is there any difference, env-wise, in the singlespec 2.7 build part compared to the plain original package?
are you sure you are running the right nosetests? they are somewhat problematic. the safest at the moment is either "%python_expand nosetests-%{$python_bin_suffix}" or "%python_exec -m nose"
there are no env variables being set (as of now), if that is what you're asking
I was running %python_expand %python_exec %{_bindir}/nosetests-%{$python_version}. Both this and %python_exec -m nose end with a "Unknown option s in python_expand()", while %python_expand nosetests-%{$python_bin_suffix} end with "Unknown option s in python_expand()", "Unknown option m in python_exec()" and "Unknown option m in python_expand()". All three of the above fail a test in the form of a "UnicodeDecodeError", which wasn't originally a problem in the plain python 2.x package. Regards -- View this message in context: http://opensuse.14.x6.nabble.com/python-singlespec-how-to-convert-your-packa... Sent from the opensuse-packaging mailing list archive at Nabble.com. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org