There's an issue about that: https://bitbucket.org/pygame/pygame/issues/174/pygame-20-the-sdl2-edition
The current thinking is that we might bless pygame_sdl2 as the recommended SDL2 version of pygame, and try to share code where it's practical. On 16 December 2016 at 17:16, Jake b <ninmonk...@gmail.com> wrote: > I thought 2.0 was for when pygame uses SDL 2.0 > > On Tue, Dec 13, 2016 at 12:58 PM, DiliupG <dili...@gmail.com> wrote: > >> congratulations on this! LONG OVERDUE! >> >> next Pygame 2.0.... >> >> Lets's skip the 1.9.3, 1.9.4, 1.9.agony-of-waiting, and jump straight to >> the future! >> >> Congratulations to all involved once again! >> >> :) >> >> On Tue, Dec 13, 2016 at 7:32 PM, Thomas Kluyver <tak...@gmail.com> wrote: >> >>> We're pleased to announce the release of Pygame 1.9.2, available now >>> from PyPI and Bitbucket. You can (probably) install it with: >>> >>> pip install pygame >>> >>> The highlights of this version include Python 3 support, and pre-built >>> wheel packages available on PyPI for major platforms, allowing convenient >>> installation with pip. I'm not sure of all the other changes, but there's >>> lots more detail in the WHATSNEW file in the source tree, or the commit >>> history. >>> >>> If you run into problems, please check for and report issues at: >>> https://bitbucket.org/pygame/pygame/issues?status=new&status=open >>> >>> We're already aware of an issue with the mixer_music_test crashing on >>> Linux when installed from a wheel (issue 317). >>> >>> Thanks, >>> Thomas >>> >> >> >> >> -- >> Kalasuri Diliup Gabadamudalige >> >> https://dahamgatalu.wordpress.com/ >> http://soft.diliupg.com/ >> http://www.diliupg.com >> >> ************************************************************ >> ********************************** >> This e-mail is confidential. It may also be legally privileged. If you >> are not the intended recipient or have received it in error, please delete >> it and all copies from your system and notify the sender immediately by >> return e-mail. Any unauthorized reading, reproducing, printing or further >> dissemination of this e-mail or its contents is strictly prohibited and may >> be unlawful. Internet communications cannot be guaranteed to be timely, >> secure, error or virus-free. The sender does not accept liability for any >> errors or omissions. >> ************************************************************ >> ********************************** >> >> > > > -- > Jake >
