pygame  committed 375e927

prep for 0.5

  • Participants
  • Parent commits 24f25a0
  • Branches default

Comments (0)

Files changed (7)

 surfarray module
-	will swap the red and blue planes for you in some blitting
-	conditions. also have noticed the occasional crash with a
-	few combinations of bit depths and array types. (volunteers?)
+	still some problems on big endian architectures (non-intel)
 Keep your eye out for more! :]
- And a big hand to everyone else who gave me appreciation,
- advice, and suggestions, especially the good folks on the
- old PySDL mailing list.
   -- Pete Shinners			<>
-Version: 0.4
-December 13, 2000
+Version: 0.5
+January 6th, 2000
 Quick installation instructions can be found in the file "install.txt"
-in this directory. Look in the docs directory for an "install.txt" with
-further details.
+in this directory. Look in the docs directory for "fullinstall.txt"
+with further details.
-With the 0.4 release things are looking really good. We've reached
+With the 0.5 release things are looking really good. We've reached
 the point where full python games are approachable with pygame.
 Thanks to all that have helped push things along this far. 
-(Especially coming through the bumpy road that was 0.2 through 0.3)
+We plan on moving up to version 1.0 within a couple months.
 pygame is a cross-platfrom library designed to make it easy to write
+The core modules of pygame are becoming pretty solid. With this
+0.5 release things are quickly approaching the 1.0 mark. After
+this I'm planning to release pygame 0.9 when SDL reaches version
+1.2. (this should happen around end of January). Pygame 0.9 will
+be a release candidate quickly followed by the real 1.0 release.
-Pygame is currently aiming for a 1.0 release first quarter this year (2001).
-This doesn't mean pygame is in a useless state, it is in fact getting
-quite robust.
+At the point it will help to look at pygame as if it were a 1.0
+release and see where it falls short. There's not too much more
+functionality going in before we move along to 1.0. The cursors
+module will get a bit of attention though.
-At this point the biggest needs are to get the functionality for
-all of SDL and the other libraries fully covered. We're almost there,
-but still need to get the more esoteric functions all wrapped up.
-The functions you'll need for 95% of your projects are already done.
-Until that point, consider the current interface to be a bit flexible.
-Things could change that will break code relying on older versions. Any
-changes will be easy to make. There will be warning of coming changes,
-but just know that it will likely happen.
-(with the 0.4 release, the interface cement is stiff)
+At some point it would be nice to add support for more external
+python libraries, here are some ideas
-Here are some main things i'd like to have done (or at least well
-looked at) by the time 1.0 rolls around. Most of these are ideas
-for covering other libraries and routiens SDL does not offer.
- * Support for OpenGL (need to experiment with pyopengl)
+ * Support for OpenGL (initial testing not so good)
  * Support for Piddle (drawing lines, shapes, text)
  * Surfarray with alpha and colormap support
  * Interface with PIL images
- * GUI library. There's a few out there, this is a biggie
+ * GUI library. There's a few out there
  * Simple image transforms; flip, rotate-90, double
+ * MPEG video playback with smpeg

File docs/fullinstall.txt

 Build instructions for building and installing pygame
-Nov 20, 2000
+Jan 5, 2000
 pygame is built and installed using the python distutils.
 If installing under Windows without a compiler, or without
 needing any of the pygame dependencies. You can download
-the Windows Precompiled Binaries Release. Download and
-extract this zipfile into the same directory as pygame.
-Now you don't need to worry about any of the Setup files,
-just type "python install" and you will be set.
+the Windows Precompiled Binaries Release.
+Also, you can download just the pygame dependencies precompiled.
+Download from the URL and extract into your pygame folder.
+The script will find these prebuilt binaries and ask
+if you would like to use them.
 You control the compilation of pygame with the "Setup"
 Assuming no errors stopped the install, you are good to go.
 Head to the examples directory and start trying things out.
-If you do have problems, first check the error. It is likely
-a problem with your Setup file. 
+If you do have problems compiling, first check the error. It
+is likely a problem with your Setup file. If you get errors
+while running the config script, you may have to finish editing
+the Setup file by hand. (which is well commented and pretty simple)
 Pete Shinners
 be installed. The latest version of each is recommended. Support for extra
 SDL daughter libraries is optional, but also recommended.
+If you have downloaded the complete windows binary download, there is no
+need to run the configure script. That distribution comes with everything
+you need preconfigured.
 The basic way to get pygame compiled and installed is to run the included
 "" script. This will do a reasonably automated config for your
 platform type. eventually this will create a customized copy of the ""
 its own "Setup" file that you will want to use.
 On Unix systems, the Setup file will be configured for the SDL dependency,
-but other dependencies may need more work. There is a chance the Setup will
+as well as hunt for the optional ones. There is a chance the Setup will
 work as-is if all dependencies have been installed similarly. Otherwise
 configure the dependencies by hand and comment out the optional modules
 which you don't have dependencies for.
 setup (name = "pygame",
-       version = '0.4',
+       version = '0.5',
        maintainer = "Pete Shinners",
        maintainer_email = "",
        description = "Python Game Development module",