Remaining release-critical issues
Ludwig Hähne
I reviewed the outstanding issues marked for release 0.1 today. I took
the liberty to change the Muppy Test docstrings to unify the test output
(Issue 17). The PySizer site is available again (Issue 18), and the
Python2.4 problem in setup.py seems to be fixed by Jean (Issue 19). The
three issues have been closed, feel free to reopen them if you disagree.
I'd like to let Robert comment on Issue 20. If it is not possible to fix
this without changing the test infrastructure, we could leave it alone
for now. I'd argue that this isn't release-critical, and we could work
on a more general solution for separating individual tests for the next
release (if that is actually the problem).
About uninstalling: Unfortunately, there does not seem to be a sane way
to uninstall manually installed Python modules like Pympler. What I have
done in the past, was to record the installed files with the record switch:
$ python setup.py install --record=install.log
Then uninstalling works like that:
$ xargs -a install.log rm -f
This is ok if you just want to install, test and immediately uninstall.
However, it is everything but pretty and you need to keep the log file
(and remember where) to uninstall. After all, you could as well look
where the files are stored and remove them.
Comments?
Ludwig
Jean Brouwers
thing holding that up may be the Sphinx issue Robert ran into. It
would be best if that were resolved although thatt is unlikely to
involve any released files.
/Jean
Robert Schuppenies
> Excellent! Prima! Looks like we are good to go for rc1. The one
> thing holding that up may be the Sphinx issue Robert ran into. It
> would be best if that were resolved although thatt is unlikely to
> involve any released files.
Please don't wait for me with rc1. The sphinx issue is just a
developer issue and seems to be only on my side. It does not
interfere with the usage of Pympler.
Jean Brouwers
Running unittests (32-bit Python 2.6.1)
=======================================
Python 2.6.1 (r261:67515, Dec 5 2008, 12:04:55)
32-bit [GCC 4.0.1 (Apple Computer, Inc. build 5367)]
Test asizeof.flatsize() vs sys.getsizeof() ... ok
Test referent identification. ... ok
Test garbage annotation. ... ok
Test pruning of reference graph. ... ok
Test serialization of log data. ... ok
Test background monitoring. ... ok
Test footprint description. ... ok
Test existence and value of snapshot members. ... ok
Test timestamp of snapshots. ... ok
Test modifying name. ... ok
Test detaching from tracked classes. ... ok
Test lifetime of tracked objects. ... ok
Test registering objects by name. ... ok
Test tracking objects through classes. ... ok
Test tracking new style classes. ... ok
Test lifetime of tracked objects. ... ok
Test mixed instance and class tracking. ... ok
Test recursive sizing and saving of referents. ... ok
Test registering objects by name. ... ok
Test object registration. ... ok
Test intrackable objects. ... ok
Test that only valid codepoints are returned. ... ok
Test if the diff of to object lists is correct. ... ok
Test that only elements within the specified size boundaries ... ok
Test that only elements of a certain type are included, ... ok
Test that referents are included in return value. ... ok
Test that the return value is the sum of the size of all objects. ... ok
Test that (non-)container objects are identified correctly. ... ok
Test that objects returns a non-empty list. ... ok
Test that this operations returns a duplicate-free lists. ... ok
Test that objects are sorted by size. ... ok
Test reference browser tree representation. ... ok
Test node functionality. ... ok
Test that the right representation is returned. ... ok
Test that a single object's data is correctly subtracted from a summary. ... ok
Test summarize method. ... ok
Test summary diff. ... ok
Test that all and only empty entries are removed from a summary. ... ok
Test that all objects of a summary are traversed. ... ok
Test object tracker diff. ... ok
Test object tracker. ... ok
Test that a summary is created correctly. ... ok
Test that the diff is computed correctly. ... ok
Test that a summary is stored under the correct key and most ... ok
----------------------------------------------------------------------
Ran 44 tests in 83.659s
OK
Robert Schuppenies
Jean Brouwers
week there were 2 so far and the week is not over yet ;-).
/Jean
But, keep in mind I usually build Python on MacOS X 10.4.11 (Tiger,
which is the one before the latest, Leopard) and run the Python,
Pympler and some of my own tests.
Occasionally, there is a failure not seen before, like with 3.0rc3 the
other day (and still in the final 3.0 release ;-).