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

Documentation: Fail to generate screen on Mac Mojave (PyGame) #374

Closed
CaseyFaist opened this issue Oct 4, 2019 · 9 comments
Closed

Documentation: Fail to generate screen on Mac Mojave (PyGame) #374

CaseyFaist opened this issue Oct 4, 2019 · 9 comments
Labels

Comments

@CaseyFaist
Copy link
Contributor

@CaseyFaist CaseyFaist commented Oct 4, 2019

When using Python 3.7 on Mojave, ppb will run but generate a blank window.

This is not an issue with PPB itself, but will trip up a PPB user. The steps to unblock a user are not complicated - I resolved by using pip3 and python3 - but could be difficult to debug for programmers new to PyGame and unfamiliar with the problem. Problems they may face are what should they searching for, why do they need to specify python3 if their .venv specifies python 3.7 and the python repl successfully loads, etc.

Docs in a "Known Issues" section (either on readthedocs, here, or both) could help these users.

Sources:

https://stackoverflow.com/questions/52718921/problems-getting-pygame-to-show-anything-but-a-blank-screen-on-macos-mojave

pygame/pygame#555

@CaseyFaist
Copy link
Contributor Author

@CaseyFaist CaseyFaist commented Oct 4, 2019

I'm happy to write these docs if I can get some direction on where y'all would want them to live 😄

Options:

  • Separate Mojave-specific getting-started.rst + link at the top of the main one
  • Bug-specific blurb in the getting-started.rst or elsewhere
  • Bug specific blurb in a "known issues" section somewhere, with relevant links in getting-started
  • Something I haven't thought of (which is most things)

Let me know! <3

@AstraLuma
Copy link
Member

@AstraLuma AstraLuma commented Oct 4, 2019

To be clear: This is specifically an incompatibility with PyGame1 and MacOS Majove?

Sounds similar to the warnings we've been putting in our release notes about Python 3.8.

@AstraLuma
Copy link
Member

@AstraLuma AstraLuma commented Oct 4, 2019

Yes, a warning early in the docs would be good. The list of incompatibilities is getting long and I'm starting to get grumpy with PyGame as a project.

@AstraLuma
Copy link
Member

@AstraLuma AstraLuma commented Mar 16, 2020

Hopefully this will be fixed by #377/#387.

@AstraLuma
Copy link
Member

@AstraLuma AstraLuma commented Mar 21, 2020

Ok, with #387 merged, the underlying issues with this bug should be fixed?

@AstraLuma
Copy link
Member

@AstraLuma AstraLuma commented Mar 29, 2020

@pathunstrom @CaseyFaist this has been fixed on mac, right?

@pathunstrom
Copy link
Collaborator

@pathunstrom pathunstrom commented Apr 12, 2020

I don't have a mojave mac to test on. But we should check on this.

@AstraLuma
Copy link
Member

@AstraLuma AstraLuma commented Mar 27, 2021

Can I get an update on this?

@AstraLuma
Copy link
Member

@AstraLuma AstraLuma commented Oct 1, 2021

We think this fixed itself and Mojave is about as dead as outsiders can tell.

@AstraLuma AstraLuma closed this Oct 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants