[IPython-dev] Extensions/pydb_ipy.py added
Ville M. Vainio
vivainio at gmail.com
Sat Oct 28 08:41:33 EDT 2006
On 10/28/06, R. Bernstein <rocky at panix.com> wrote:
> But one other thing regarding call_pydb(). And I'm not really sure how
> to fix. So if anyone has suggestions...
>
> pydb.runv() should be using the ipython Pdb class which has pdef, pdoc
> commands added and not the pydb one.
Would it make sense to import pydb.pydb module in pydb_ipy.py, and
inject the ipython version of Pdb class to the pydb module namespace?
That way main() would instantiate the ipython version...
> > Ok; though does the existence of *list syntax not make pydb.runv()
> > slightly redundant?
>
> Well, in the os module there is:
> execl( path, arg0, arg1, ...)
> execle( path, arg0, arg1, ..., env)
> execlp( file, arg0, arg1, ...)
> execlpe( file, arg0, arg1, ..., env)
> execv( path, args)
> execve( path, args, env)
> execvp( file, args)
> execvpe( file, args, env)
>
> spawnl( mode, path, ...)
> spawnle( mode, path, ..., env)
> spawnlp( mode, file, ...)
> spawnlpe( mode, file, ..., env)
> spawnv( mode, path, args)
> spawnve( mode, path, args, env)
> spawnvp( mode, file, args)
> spawnvpe( mode, file, args, env)
>
> The "run" suffixes were drawn from this (which in turn are drawn from
> the C library system calls.)
Those functions were introduced long before *arglist syntax (on caller
side)... I'm not sure whether anyone actualle "likes" those functions
anymore. In C they make perfect sense, of course.
--
Ville M. Vainio - vivainio.googlepages.com
blog=360.yahoo.com/villevainio - g[mail | talk]='vivainio'
More information about the IPython-dev
mailing list