For now, you have to use a pair of packaging tools we've written to package Ren'Py apps for Android and iOS. Despite the names, they're both intended to package arbitrary pygame_sdl2 apps. (For now, there is some Ren'Py branding, especially in the iOS tool, but that branding should probably be changed before release anyway.)
RAPT (Ren'Py Android Packaging Tool) still works approximately as documented atÂ
http://pygame.renpy.org/, especially when it comes to building android applications. The big change is that the lifecycle events are now different Â- see below. (Some other modules, like lifecycle management, are also different.)
Renios is the iOS packaging tool. You can create a new project by runningÂ
  ./ios.py create MyProject
That will copy the prototype directory to MyProject, and make some changes to the various plist files. You can then place a main.py in MyProject/base, and use Xcode to build the project.
We've exposed the SDL2 application lifecycle events to pygame_sdl2 users:
The mapping is pretty straightforward -ÂSDL_APP_TERMINATING becomes pygame_sdl2.APP_TERMINATING. In Ren'Py, I handle these as follows:
On APP_TERMINATING, we save the game (in a special save file) and immediately quit.
On APP_WILLENTERBACKGROUND, we stop all sound, timers, and screen updates; save the game (in a special save file), and sit in a tight pygame.event.wait() loop. If that loop gets an APP_DIDENTERFOREGROUND event, we delete the save file, and resume screen updates and sound. If the loop gets an APP_TERMINATING event, we just quit.
When Ren'Py starts, it checks for the special save file, and if found loads it, restoring the player's state.
Right now, the mobile stuff is still somewhat raw. RAPT has been used to ship a number of Android apps, so it works well enough - but I haven't spent a lot of time trying it with arbitrary pygame_sdl2 games, so there might be some minor problems there. Renios is still quite beta. Both are Python 2.7-only at the moment - making the version of python configurable will be a challenge.