-> > Can you give an example of circumstances where the index would be
-> > useful?  I can't imagine one on my own.
->
-> Sorry for the length.
->
-> I am working on an app that has a user authentication part. I need the
-> following paths:
->
-> /config/
-> returns a page with all the configuration commands
->
-> /config/users
-> returns a page with the list of all the known users
->
-> /config/user/add
-> returns a form with empty fields for a new user
->
-> /config/user/[loginName]/modify
-> returns a form with current values for a known user
->
-> /config/user/validate
-> used as a form action, validates values for a added or modified user
->
-> /config/user/[loginName]/delete
-> deletes a known user

I'm very confused by your code ;).

I'd do something like:  (dir/package structure)

config/__init__.py -- contains _q_index with all config commands, and
        'users' func;

config/user/__init__.py -- contains _q_index with general user commands,
        exports 'add' func and _q_getname func that returns UserCommands
        object for 'username'

UserCommands object: loads username, exports 'modify', 'delete'.

What am I missing?  I'd probably put 'validate' on UserCommands, too.

Keeping track of the current URL "level" is a bad thing, because it reduces
modularity...

--titus