[Python-Dev] Proposed unittest changes (original) (raw)
Michael Foord fuzzyman at voidspace.org.uk
Mon Jul 14 16:21:47 CEST 2008
- Previous message: [Python-Dev] Proposed unittest changes
- Next message: [Python-Dev] Proposed unittest changes
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Raymond Hettinger wrote:
Michael Foord <fuzzyman at voidspace.org.uk> writes:
The full list of changes proposed (feel free to start - but ping me or the list) and not shot down was something like: […] Thanks. I'm working these into another draft PEP that I hope to have up in a day or two. Given all of the language changes in 2.6 and 3.0, I would think that it is dangerous to make any changes at all to the unittest API. That module is the one anchor in a sea of change. As proposed the changes don't remove or rename anything - so there will be no code breakage, just additional test methods.
However, as we're into the beta phase I don't think these changes can make 2.6 / 3.0 anyway.
Michael
Raymond
Python-Dev mailing list Python-Dev at python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk
-- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/ http://www.trypython.org/ http://www.ironpython.info/ http://www.theotherdelia.co.uk/ http://www.resolverhacks.net/
- Previous message: [Python-Dev] Proposed unittest changes
- Next message: [Python-Dev] Proposed unittest changes
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]