pygame 2 has a lot of new things.

But we need to tell people about all the new goodies.

We need:

• small paragraphs of text explaining exciting features.
• tweet sized texts explaining new stuff
• benchmarks
• mini examples of how to use the new stuff

How to find what's new anyway?

• have a look at closed pull requests
• have a look at the SDL2 what's new annoucements
• ask people

After an email discussion with @tmontes , I guess we need a constitution for Mu so folks can see what rules (both technical and community) we follow, what we expect from contributors and so we can hold ourselves to account.

I'm very much for making things open and clear.

At the very least it should include:

• Rules of the road we (as admins) follow,
• Our expectations of contributors,

This may be a lack of grokking Chipmunk, but I noticed that calling Space.add_collision_handler with *(a, b) and *(b, a) gave different handlers, but only one's separate handler was ever called.

Is the ordering significant? I tried swapping the order that I added collision handlers, but it always picked the same one (ie. not just the last one defined).

This isn't a complete sample

You can use the built-in python argparse module or the click library to allow people to pass in things like the images to use for the body and for the eyes as arguments.

For example python face_track.py --background=base.png --eyes=eyes.png

This is a usability win because it lets people experiment with the func

Better detection and error messages for invalid values during Actor initialization would be useful to aid users in debugging.

Expected result:
Better and consistent error messages to aid in debugging and catch obvious invalid values.

Actual result:
The error messages are confusing (for beginner programmers) and inconsistent. And in one case the error is not detected at all.

Here are s

We have several screen with TextEntry and shortcut for button. We cannot have the focus on the TextEntry when we open the dialog and continue to use letter as shortcut. They will conflict.

So we need to take a decision and stay coherent (which is not the case).

1/ Add another touch (modifier) for shortcut i.e. Ctrl or Shift

2/ Don't let TextEntry have the focus at opening. We can add a gl

before you start the game you should be able to select a map

With pygame, one can call the set_mode() with display flags: https://www.pygame.org/docs/ref/display.html#pygame.display.set_mode

Currently the EzPyGame's Application class has no way to read and write these flags, so a property should be added for each possible flag:

pygame.FULLSCREEN    create a fullscreen display
pygame.DOUBLEBUF     recommended for HWSURFACE or OPENGL
pygame