Skip to content
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

Please delete dysfunctional Python 3.12 windows-curses build from PyPI #52

Closed
daver1691 opened this issue Feb 28, 2024 · 4 comments
Closed
Labels
bug Something isn't working

Comments

@daver1691
Copy link

If there's nobody to maintain this package, then so be it, but can somebody please delete the dysfunctional Python 3.12 windows-curses wheel from PyPI, and remove the info on its PyPI web page saying it's compatible with Python 3.12.

It's a whole lot better for people to be supplied nothing when they try to install windows-curses, than be supplied something that silently exits when they try to use it. I've seen people on the beginner's subreddit "learnpython" saying that windows-curses "does nothing" and "does not work". If they knew that they had to downgrade to Python 3.11 to use it, that would be something.

@kaecy
Copy link

kaecy commented Mar 7, 2024

Pretty sure that's a python problem not a project issue. Lots of projects have stopped working with python 3.12 including wxpython.

@Ddhruv-IOT
Copy link

Pretty sure that's a python problem not a project issue. Lots of projects have stopped working with python 3.12 including wxpython.

If there's nobody to maintain this package, then so be it, but can somebody please delete the dysfunctional Python 3.12 windows-curses wheel from PyPI, and remove the info on its PyPI web page saying it's compatible with Python 3.12.

It's a whole lot better for people to be supplied nothing when they try to install windows-curses, than be supplied something that silently exits when they try to use it. I've seen people on the beginner's subreddit "learnpython" saying that windows-curses "does nothing" and "does not work". If they knew that they had to downgrade to Python 3.11 to use it, that would be something.

Thanks for this, it worked, I was on py12, then I downgrade to Py11.

@spudpiggy
Copy link

I thought this module was fake for a second, but this is even dumber.
Remove the 3.12 build. It does not exist.
By releasing fake builds, you are lying to users and damaging your reputation.

(i know this seems extreme but it's such a bafflingly bad idea i can't help but be mad abt it)

@stephanosio stephanosio added the bug Something isn't working label May 5, 2024
@stephanosio
Copy link
Member

v2.3.3, which fixes #50, has been released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants