[IPython-dev] Release plans...

[Fernando Perez]

On 4/5/07, Dan Milstein <danmil at comcast.net> wrote:

> Yep, that's correct -- and I've actually added a whole set of further
> tests in my private copy to ensure that it does the right thing for
> all trailing qmark / leading esc char combos:
>
>      # Trailing qmark combos.  Odd special cases abound
>      ( '!thing?',   handle_shell_escape), # trailing '?' loses to
> shell esc
>      ( '!thing ?',  handle_shell_escape),
>      ( '!!thing?',  handle_shell_escape),
>      ( '%cmd?',     handle_help),
>      ( '/cmd?',     handle_help),
>      ( ';cmd?',     handle_help),
>      ( ',cmd?',     handle_help),

OK, here's the current diff then after applying these:

Index: test_prefilter.py
===================================================================
--- test_prefilter.py	(revision 2218)
+++ test_prefilter.py	(working copy)
@@ -145,8 +145,15 @@
     ( '?thing',    handle_help,  ),
     ( 'thing?',    handle_help ),  # '?' can trail...
     ( 'thing!',    handle_normal), # but only '?' can trail
-    ( '!thing?',   handle_help),   # trailing '?' wins if more than one
     ( '   ?thing', handle_help),   # ignore leading whitespace
+    # Trailing qmark combos.  Odd special cases abound
+    ( '!thing?',   handle_shell_escape), # trailing '?' loses to shell esc
+    ( '!thing ?',  handle_shell_escape),
+    ( '!!thing?',  handle_shell_escape),
+    ( '%cmd?',     handle_help),
+    ( '/cmd?',     handle_help),
+    ( ';cmd?',     handle_help),
+    ( ',cmd?',     handle_help),
     ( '!ls',       handle_shell_escape ),
     ( '%magic',    handle_magic),
     # Possibly, add test for /,; once those are unhooked from %autocall


I'll do a commit later tonight.

Thanks!

f