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
Compliance with PEP 517 #148
Comments
there's a pull, but if the guy doesn't reply, we might need to fork off the project. |
As long as pr is not accepted, installation can be done as follows:
pip install playsound@git+https://github.com/taconi/playsound
poetry add playsound@git+https://github.com/taconi/playsound |
How backwards compatible is this?AFAIK, the current setup works in the latest version of Python and there’s no plans to ever break it. If they were to ever break it, I’d expect that to be in a Python 4 which is hopefully still far away.I believe playsound works all the way back to Windows XP on something like Python 2.3 (IDK, maybe it’s only up to 2.7). Although I’ve personally switched to exclusively using Python 3.7 and newer, I’d rather maintain compatibility with a much wider range if it’s not too difficult to do so.So… sell me on why this change is needed, beyond that it’s a newer thing that could be adopted. I could adopt f-strings in the project, too. I certainly like them on my projects where I don’t care about maintaining backwards compatibility. Type annotations are cool, too. I’d sooner adopt type annotations (as a quality measure), then switching to toml just for the sake of it.Sent from my iPhoneOn Nov 18, 2023, at 21:12, taconi ***@***.***> wrote:
As long as the pr is not accepted, the installation can be done this way:
pip install ***@***.***+https://github.com/taconi/playsound
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
It would be more of a question of installation, in version 23.1 (2023-04-15) of pip support has been removed from
This version of pip only supports python >= 3.7 so <=3.6 would no longer be supported. However, the latest versions of pip and poetry no longer support Can I add |
I added |
@TaylorSMarks are you still out there? This fix would make the lib more accessible to python poetry users. |
The setuptools is treating setup.py as legacy after introducing pyproject.toml in PEP 517 and PEP 518.
The text was updated successfully, but these errors were encountered: