Open milahu opened 2 years ago
Hi there milahu,
unfortunately, I was unable to reproduce the problem you ran into. The files downloaded via pip should be taken directly from the PyPI.
If you take a look at the source code (specifically the setup.py
file), you may notice it only officially supports Python <= 3.8
.
# Specify the Python versions you support here. In particular, ensure
# that you indicate whether you support Python 2, Python 3 or both.
'Programming Language :: Python :: 2',
'Programming Language :: Python :: 2.7',
'Programming Language :: Python :: 3',
'Programming Language :: Python :: 3.3',
'Programming Language :: Python :: 3.4',
'Programming Language :: Python :: 3.5',
'Programming Language :: Python :: 3.6',
'Programming Language :: Python :: 3.7',
'Programming Language :: Python :: 3.8',
There is no particular reason why it should not support any more recent Python versions. It's just not been updated in quite a while. I don't think pip actually checks this, but I don't know for certain.
You may also notice that the version number is indeed correct in that particular setup.py
file.
version='0.6.14a1',
The reason for this is simple. I used to publish all my libraries manually from my local machine and often forgot to push the version change. As for why there has not been an update for so long, well I have a lot of stuff on my to-do list already and I only get to work on that when I have free time (which there is also not very much of lately). I haven't heard from @mattgwwalker, but I'm sure he also has other stuff to do.
Could you please try downloading the source release from PyPI directly and installing it manually via pip?
that was way more attention that this issue deserves ^^ i just wanted to share my workaround, in the rare case that someone else runs into the same error but yeah, using source from pypi should work
stt requires pyogg with
but this throws
why?
setup.py says
version='0.6.13a1'
(13 != 14)workaround: fix version in setup.py