Rev 146: CHANGES.txt updates, summarizing the log info. in http://bazaar.launchpad.net/~meliae-dev/meliae/trunk

[John Arbash Meinel]

At http://bazaar.launchpad.net/~meliae-dev/meliae/trunk

------------------------------------------------------------
revno: 146
revision-id: john at arbash-meinel.com-20100630214455-2mpjbggxot4vly80
parent: john at arbash-meinel.com-20100630213218-ou2ur4hr40p4lp3v
committer: John Arbash Meinel <john at arbash-meinel.com>
branch nick: trunk
timestamp: Wed 2010-06-30 16:44:55 -0500
message:
  CHANGES.txt updates, summarizing the log info.
-------------- next part --------------
=== modified file 'CHANGES.txt'
--- a/CHANGES.txt	2010-01-08 23:11:04 +0000
+++ b/CHANGES.txt	2010-06-30 21:44:55 +0000
@@ -5,10 +5,26 @@
 .. contents:: List of Releases
    :depth: 1
 
-Meliae 0.2.1 (not released yet)
-###############################
-
-:0.2.0: (not released yet)
+Meliae 0.2.1rc1
+###############
+
+:0.2.1rc1: (not released yet)
+
+* Avoid calling ``PyType_Type.tp_traverse`` when the argument is not a
+  heap-class. There is an assert that gets tripped if you are running a
+  debug build (or something to do with how Fedora builds its python).
+  (John Arbash Meinel, #586122)
+
+* Flush the file handle before exiting. We were doing it at the Python
+  layer, but that might not translate into the ``FILE*`` object.
+  (John Arbash Meinel, #428165)
+
+* Handle some issues when using Pyrex 0.9.8.4. It was treating
+  ``<unsigned long>`` as casting the object pointer, not as a Python
+  level "extract an integer". However, assignment to an ``cdef unsigned
+  long`` does the right thing. (John Arbash Meinel)
+
+* Tweak some memory performance issues (Gary Poster, #581918)
 
 
 Meliae 0.2.0