-
-
Notifications
You must be signed in to change notification settings - Fork 141
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
pygame-ce requirement #460
Comments
It is there any compatibility issues if I migrate to |
No compatibility issues for me. I replaced it (as it has been advised in the 2.2.0 release), but if you have specific doubts/questions, then you can ask directly on |
Hello! I would not be happy if pygame-menu will move its base to pygame-ce. I think you can just make a fork of pygame-menu, but optimise it for pygame-ce. |
I also agree with @leestarb, because it breaks compatibility with many projects that rely on this library, as well as it deprecates python 3.6 #450. Thus, I've created a new branch that will be updated after each version. See https://github.com/ppizarror/pygame-menu/tree/pygame-ce. All pygame-menu tests have successfully passed.. so I'll create a new version v4.4.1, today, publishing both |
Thank you so much! @ppizarror |
@JaskRendix , check out the brand new https://pypi.org/project/pygame-menu-ce/ |
Hello there,
I noticed that in your requirements.txt there is
pygame>=1.9.3
Have you considered to switch to pygame-ce?
It is a fork of the upstream pygame project by its former core developers, and was created after impossible challenges prevented them from continuing development upstream. The new distribution aims to offer more frequent releases, continuous bugfixes and enhancements, and a more democratic governance model.
A couple of days ago they release a new version 2.2.0 and it fixes a lot of issues.
The community is very active.
The text was updated successfully, but these errors were encountered: