From 1ff37207a22795254b8840a56223987bf3b47468 Mon Sep 17 00:00:00 2001
From: holger krekel <holger@merlinux.eu>
Date: Wed, 13 Jan 2010 18:20:38 +0100
Subject: [PATCH] another wish

--HG--
branch : trunk
---
 ISSUES.txt | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/ISSUES.txt b/ISSUES.txt
index 8f30bfd18..7be0f6274 100644
--- a/ISSUES.txt
+++ b/ISSUES.txt
@@ -97,3 +97,13 @@ have docs living with the plugin and require them to
 be available on doc generation time, at least when 
 the target is the website?  Or rather go for interactive help? 
 
+improved reporting on funcarg usage / name mismatches
+----------------------------------------------------------------
+tags: feature 1.2
+
+see to improve help and support for funcarg usage, 
+i.e. when a funcarg does not match any provided one. 
+Also consider implementing py.test --funcargs to
+show available funcargs - it should honour the 
+path::TestClass syntax so one can easily inspect
+where funcargs come from or which are available.