-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Adding audioop-lts for python >=3.13 #816
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @taconi can you remove the
- PYTHON: "C:/Python34"
FFMPEG: "4.2.3"
block in appveyor.yml?
That pip version is ancient (doesn't understand your 3.13 condition), so the tests fail to install setup.py.
|
@reneleonhardt @jiaaro Will support for 3.4 be removed? |
|
I'm no maintainer, just saying that if you want to support 3.13 you have to drop unsupported versions anyway 😅 |
|
That's fine - 3.4 released in 2014 |
|
Sadly the "newer" pip still fails with |
I installed it locally with python 3.13 and ran the tests and it worked. I think it's something to do with pip, the other versions are running with pip==19.3.1 (including python 2.7) and even updating pip in the pipeline the latest version available for python 3.4 is pip==19.1. |
|
Yes, Python 3.4 was updating pip to 19.1.1... and still failed: |
The server running the tests (AppVeyor) does not have python versions 3.9, 3.10, 3.11, 3.12 and 3.13. I've never worked with this CI, so I don't know if it needs any configuration One option, as commented in issue #827 (#827 (comment) and #827 (comment)), is to move the CI to Github Actions. What do you think @Jairo ? From what I understand there are two CI, appveyor.yml to run on windowns and .travis.yml to run on linux. |
|
It was just a question, I don't need AppVeyor (Windows) personally, Travis would be enough for me 😅 If Python 3.9 is not available then you're probably using an at least 8 years old Visual Studio 2017 image (or below): |
|
@taconi I have no permissions, can you see if travis really hasn't finished yet... after 24h? 🤣 A new release would be great, after https://github.com/huggingface/transformers/releases/tag/v4.51.1 pydub seems to be the only thing left for Python 3.13 support in Aider-AI/aider#3037 💚 |
I don't have permission to see it either.
I'll revert the changes I made to the CI. I managed to run the tests with 3.13 on my machine, but I don't know if it works on windowns. I think it would be good to tweak the CI, but until then, if anyone can run the tests with 3.13 on windowns it would be great |
|
@taconi This commit should be able to fix the problem. |
|
@medaminezghal An import is no fix if the dependency hasn't been installed, this is what this PR does 😉 |
|
@reneleonhardt the Note that I have tested the fix with gradio that depends on |
|
I didn't see that, sorry. Have you tested on Python 3.13 or 3.14rc2? |
|
@reneleonhardt I'm using Python 3.13 |
|
But no contribution matters anyway if the project isn't maintained anymore, no amount of work will be merged, it's sad if not more maintainers are being added 😞 |
The audioop library was removed in python 3.13, which caused the pyaudioop fallback to be called, but this also gives an error (I believe the import should be
import pydub.pyaudioop as audioop).Even changing the import to pydub.pyaudioop broke many tests, so I added
audioop-ltsfor python>=3.13.Closes #815