February 2010 Archives by subject

• Messages sorted by: [ thread ] [ author ] [ date ]
• More info on this list...

Starting: Mon Feb 1 13:32:43 PST 2010
Ending: Sun Feb 28 20:18:06 PST 2010
Messages: 163

• [TIP] @unittest.expectedFailure   Chris Withers
• [TIP] @unittest.expectedFailure   Benjamin Peterson
• [TIP] [OT] BoF Meeting pictures   Alfredo Deza
• [TIP] [OT] BoF Meeting pictures   C. Titus Brown
• [TIP] [OT] Goats of PyCon   Chris Lasher
• [TIP] [OT] Goats of PyCon   Terry Peppers
• [TIP] [OT] Goats of PyCon   Alfredo Deza
• [TIP] [OT] Goats of PyCon   Doug Hellmann
• [TIP] [OT] Goats of PyCon   C. Titus Brown
• [TIP] [OT] Goats of PyCon   Matt Harrison
• [TIP] [OT] Goats of PyCon   Terry Peppers
• [TIP] [OT] Goats of PyCon   Paul McLanahan
• [TIP] [OT] Goats of PyCon   Jesse Noller
• [TIP] [OT] Goats of PyCon   Ned Batchelder
• [TIP] [OT] Goats of PyCon   Andrew Dalke
• [TIP] [OT] Goats of PyCon   Olemis Lang
• [TIP] [OT] Goats of PyCon   Raphael Marvie
• [TIP] [OT] Goats of PyCon   Olemis Lang
• [TIP] [OT] Goats of PyCon   Ben Finney
• [TIP] [OT] Goats of PyCon   Michael Foord
• [TIP] [OT] Goats of PyCon   Ben Finney
• [TIP] [OT] Goats of PyCon   Michael Foord
• [TIP] [OT] Goats of PyCon   Doug Hellmann
• [TIP] [OT] Goats of PyCon   Andrew Dalke
• [TIP] [OT] Goats of PyCon   Benjamin Scherrey
• [TIP] [OT] Goats of PyCon   Andrew Bennetts
• [TIP] [OT] Goats of PyCon   Michael Foord
• [TIP] [OT] wish I was still at pycon   Kumar McMillan
• [TIP] [OT] wish I was still at pycon   Olemis Lang
• [TIP] [OT] wish I was still at pycon   C. Titus Brown
• [TIP] [OT] wish I was still at pycon   adinel chirita
• [TIP] alphabetical order in testing   Felix Schwarz
• [TIP] Announce: Linux Desktop Testing Project (LDTP) 1.7.2 released   Nagappan Alagappan
• [TIP] Announce: Linux Desktop Testing Project (LDTP) 2.0.3 released   Nagappan Alagappan
• [TIP] Announce: Pygora 0.0.1   Alfredo Deza
• [TIP] Announce: testresources 0.2.4   Robert Collins
• [TIP] Announce: testresources 0.2.4   Michael Foord
• [TIP] Announce: testresources 0.2.4   Robert Collins
• [TIP] Announcing: Deep Agile 2010: Empowering Teams with Agile Games   Bob Clancy
• [TIP] AST instrumentation (was Re: branch coverage)   Andrew Dalke
• [TIP] AST instrumentation (was Re: branch coverage)   Ned Batchelder
• [TIP] Defining a convention for running tests, #2   C. Titus Brown
• [TIP] Defining a convention for running tests, #2   Michael Foord
• [TIP] Defining a convention for running tests, #2   Michael Foord
• [TIP] Defining a convention for running tests, #2   Robert Collins
• [TIP] Defining a convention for running tests, #2   Michael Foord
• [TIP] Defining a convention for running tests, #2   Robert Collins
• [TIP] Defining a convention for running tests, #2   Michael Foord
• [TIP] Defining a convention for running tests, #2   Robert Collins
• [TIP] Defining a convention for running tests, #2   Michael Foord
• [TIP] Defining a convention for running tests, #2   Robert Collins
• [TIP] Defining a convention for running tests, #2   Michael Foord
• [TIP] Defining a convention for running tests, #2   Robert Collins
• [TIP] Guidelines for where to put tests & how to package them   C. Titus Brown
• [TIP] Guidelines for where to put tests & how to package them   Matt Harrison
• [TIP] Guidelines for where to put tests & how to package them   C. Titus Brown
• [TIP] Guidelines for where to put tests & how to package them   Robert Collins
• [TIP] Guidelines for where to put tests & how to package them   Michał Kwiatkowski
• [TIP] Guidelines for where to put tests & how to package them   DICAD - Rex Turnbull
• [TIP] Guidelines for where to put tests & how to package them   Nicolas Chauvat
• [TIP] Guidelines for where to put tests & how to package them   C. Titus Brown
• [TIP] Guidelines for where to put tests & how to package them   C. Titus Brown
• [TIP] Guidelines for where to put tests & how to package them   Olemis Lang
• [TIP] Guidelines for where to put tests & how to package them   Olemis Lang
• [TIP] Guidelines for where to put tests & how to package them   Barry Warsaw
• [TIP] Guidelines for where to put tests & how to package them   Olemis Lang
• [TIP] Guidelines for where to put tests & how to package them   C. Titus Brown
• [TIP] Guidelines for where to put tests & how to package them   C. Titus Brown
• [TIP] Guidelines for where to put tests & how to package them   C. Titus Brown
• [TIP] Guidelines for where to put tests & how to package them   Olemis Lang
• [TIP] Guidelines for where to put tests & how to package them   Olemis Lang
• [TIP] Guidelines for where to put tests & how to package them   Carl Meyer
• [TIP] Guidelines for where to put tests & how to package them   Michał Kwiatkowski
• [TIP] Guidelines for where to put tests & how to package them   Olemis Lang
• [TIP] Guidelines for where to put tests & how to package them   C. Titus Brown
• [TIP] Guidelines for where to put tests & how to package them   Michael Foord
• [TIP] Guidelines for where to put tests & how to package them   Michael Foord
• [TIP] Guidelines for where to put tests & how to package them   Michael Foord
• [TIP] Guidelines for where to put tests & how to package them   Olemis Lang
• [TIP] Guidelines for where to put tests & how to package them   Michael Foord
• [TIP] Guidelines for where to put tests & how to package them   Olemis Lang
• [TIP] Guidelines for where to put tests & how to package them   Michael Foord
• [TIP] Guidelines for where to put tests & how to package them   Olemis Lang
• [TIP] Guidelines for where to put tests & how to package them   Michael Foord
• [TIP] Guidelines for where to put tests & how to package them   Robert Collins
• [TIP] Guidelines for where to put tests & how to package them   Michael Foord
• [TIP] Guidelines for where to put tests & how to package them   Olemis Lang
• [TIP] Guidelines for where to put tests & how to package them   Olemis Lang
• [TIP] Guidelines for where to put tests & how to package them   Michael Foord
• [TIP] Guidelines for where to put tests & how to package them   Olemis Lang
• [TIP] Guidelines for where to put tests & how to package them   Michael Foord
• [TIP] Guidelines for where to put tests & how to package them   Carl Meyer
• [TIP] Guidelines for where to put tests & how to package them   C. Titus Brown
• [TIP] Guidelines for where to put tests & how to package them   C. Titus Brown
• [TIP] Guidelines for where to put tests & how to package them   C. Titus Brown
• [TIP] Guidelines for where to put tests & how to package them   Michael Foord
• [TIP] Guidelines for where to put tests & how to package them   C. Titus Brown
• [TIP] Guidelines for where to put tests & how to package them   C. Titus Brown
• [TIP] Guidelines for where to put tests & how to package them   Michael Foord
• [TIP] Guidelines for where to put tests & how to package them   C. Titus Brown
• [TIP] Guidelines for where to put tests & how to package them   Michael Foord
• [TIP] Guidelines for where to put tests & how to package them   C. Titus Brown
• [TIP] Guidelines for where to put tests & how to package them   C. Titus Brown
• [TIP] Guidelines for where to put tests & how to package them   Michael Foord
• [TIP] Guidelines for where to put tests & how to package them   Michael Foord
• [TIP] Guidelines for where to put tests & how to package them   C. Titus Brown
• [TIP] Guidelines for where to put tests & how to package them   C. Titus Brown
• [TIP] Guidelines for where to put tests & how to package them   Michael Foord
• [TIP] Guidelines for where to put tests & how to package them   C. Titus Brown
• [TIP] Guidelines for where to put tests & how to package them   Michael Foord
• [TIP] Guidelines for where to put tests & how to package them   Michael Foord
• [TIP] Guidelines for where to put tests & how to package them   C. Titus Brown
• [TIP] Is there nose plugin for deeper discovery?   Pete Forman
• [TIP] Is there nose plugin for deeper discovery?   jason pellerin
• [TIP] Is there nose plugin for deeper discovery?   Gary Bernhardt
• [TIP] Isolated unit testing   Gary Bernhardt
• No subject  
• No subject  
• [TIP] nose with doctests and logging   John Evans
• [TIP] nose with doctests and logging   Kumar McMillan
• [TIP] nose with doctests and logging   John Evans
• [TIP] nose with doctests and logging   Kumar McMillan
• [TIP] py.test 1.2.1 released   holger krekel
• [TIP] PyCon Conference Pass   Paul Hildebrandt
• [TIP] PyCon Conference Pass   Paul Hildebrandt
• [TIP] RFC: Barely minimal CI + tests + packaging in Python WAS: Guidelines for where to put tests & how to package them   Olemis Lang
• [TIP] RFC: Barely minimal CI + tests + packaging in Python WAS: Guidelines for where to put tests & how to package them   Fred Drake
• [TIP] RFC: Barely minimal CI + tests + packaging in Python WAS: Guidelines for where to put tests & how to package them   Olemis Lang
• [TIP] RFC: Barely minimal CI + tests + packaging in Python WAS: Guidelines for where to put tests & how to package them   Olemis Lang
• [TIP] RFC: Barely minimal CI + tests + packaging in Python WAS: Guidelines for where to put tests & how to package them   Olemis Lang
• [TIP] RFC: Barely minimal CI + tests + packaging in Python WAS: Guidelines for where to put tests & how to package them   Olemis Lang
• [TIP] starting testrun.org for testing in python   holger krekel
• [TIP] starting testrun.org for testing in python   holger krekel
• [TIP] starting testrun.org for testing in python   Michael Foord
• [TIP] starting testrun.org for testing in python   Olemis Lang
• [TIP] starting testrun.org for testing in python   holger krekel
• [TIP] starting testrun.org for testing in python   Michael Foord
• [TIP] starting testrun.org for testing in python   Olemis Lang
• [TIP] starting testrun.org for testing in python   Olemis Lang
• [TIP] starting testrun.org for testing in python   holger krekel
• [TIP] starting testrun.org for testing in python   holger krekel
• [TIP] TIP IRC Channel (#python-testing on freenode)   Eric Holscher
• [TIP] TiP Open Space PyCon (Broken Record)   Terry Peppers
• [TIP] TIP/PyCon Open Space   Terry Peppers
• [TIP] unittest issues and development   Michael Foord
• [TIP] unittest issues and development   Fernando Perez
• [TIP] unittest issues and development   Michael Foord
• [TIP] unittest issues and development   Fernando Perez
• [TIP] unittest issues and development   Michael Foord
• [TIP] unittest issues and development   Jonathan Lange
• [TIP] unittest issues and development   Michael Foord
• [TIP] unittest issues and development   Fernando Perez
• [TIP] unittest issues and development   Michael Foord
• [TIP] unittest issues and development   Fernando Perez
• [TIP] unittest issues and development   Michael Foord
• [TIP] unittest issues and development   holger krekel
• [TIP] unittest issues and development   exarkun at twistedmatrix.com
• [TIP] unittest2: backport of the new features in unittest for Python 2.7   Michael Foord
• [TIP] unittest2: backport of the new features in unittest for Python 2.7   J. Clifford Dyer
• [TIP] Using mock library (written by Michael Foord)   Максим Lacrima
• [TIP] Using mock library (written by Michael Foord)   Максим Lacrima
• [TIP] Using mock library (written by Michael Foord)   Chris Withers
• [TIP] Using mock library (written by Michael Foord)   Michael Foord

Last message date: Sun Feb 28 20:18:06 PST 2010
Archived on: Sun Feb 28 20:19:48 PST 2010

• Messages sorted by: [ thread ] [ author ] [ date ]
• More info on this list...