Be careful, the package you get via pypi is another than this one.
In fact I did the same breakage RedHat did:
https://access.redhat.com/discussions/3199512
(I stated this on #python irc, sorry for not mentioning in the changes)
About py2.., the package was not needed up to now. It will not show up on SLE12, Leap 42.3 or anything still supporting py2.
Therefore my idea was to already just limit this to py3.
I can put some time in and get this the py2/py3 compat way if this has any advantage. I thought py3 only is even better..
The singlespec advantage is mostly it works for all that are defined by the header (atm the tumbleweed still has py2) but in long run more important is it would work with pypy https://pypy.org/ (sorry i wrote pypi before as I write that down more often).
As a benefit normal singlespec package is way shorter than just one for specific flavor :)
It seems it can run under pypi and py2, lemme tweak it to full singlespec. Otherwise all looks good.
Be careful, the package you get via pypi is another than this one. In fact I did the same breakage RedHat did: https://access.redhat.com/discussions/3199512 (I stated this on #python irc, sorry for not mentioning in the changes)
About py2.., the package was not needed up to now. It will not show up on SLE12, Leap 42.3 or anything still supporting py2. Therefore my idea was to already just limit this to py3. I can put some time in and get this the py2/py3 compat way if this has any advantage. I thought py3 only is even better..
The singlespec advantage is mostly it works for all that are defined by the header (atm the tumbleweed still has py2) but in long run more important is it would work with pypy https://pypy.org/ (sorry i wrote pypi before as I write that down more often).
As a benefit normal singlespec package is way shorter than just one for specific flavor :)