From 285e79cc929b5aa45598058a378d9033aa1a38c0 Mon Sep 17 00:00:00 2001
From: Ned Batchelder <ned@nedbatchelder.com>
Date: Mon, 31 Oct 2011 07:22:23 -0400
Subject: #155 is fixed.

---
 CHANGES.txt | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/CHANGES.txt b/CHANGES.txt
index 1caa7ba3..66bf5c85 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -2,6 +2,17 @@
 Change history for Coverage.py
 ------------------------------
 
+Version 3.5.2b1
+---------------
+
+- When running a module with ``coverage run -m <modulename>``, certain details
+  of the execution environment weren't the same as for 
+  ``python -m <modulename>``.  This had the unfortunate side-effect of making
+  ``coverage run -m unittest discover`` not work if you had tests in a
+  directory named "test".  This fixes `issue 155`_.
+
+.. _issue 155: https://bitbucket.org/ned/coveragepy/issue/155/cant-use-coverage-run-m-unittest-discover
+
 
 Version 3.5.1 --- 23 September 2011
 -----------------------------------
-- 
cgit v1.2.1