On Jun 26, 2:40 pm, Craig Citro <craigci...@gmail.com> wrote:
> > Should the strings extra1, etc., be searched for only in the source
> > code, or should they be searched for both in the source code and the
> > file name?
>
> I've definitely used the "search path too" behavior on purpose at
> various times. In particular, doing things like adding "matrix" to the
> search essentially narrows the result to the sage/matrix/ directory,
> which can be handy. Of course, this is clearly a bit of a hack, and
> inconsistent (as John is pointing out). So how about instead, we
> implement what I'm actually trying to do with this -- add a "path"
> optional argument to the search_* functions. (If you're using os.walk,
> this should be pretty trivial to add, I think.) It'd be especially fun
> if you could give it the name of a module (so that I could tab
> complete), too.
>
> -cc
Good ideas. There's a patch up at
<http://trac.sagemath.org/sage_trac/ticket/6429>
Please try it out, especially if you have access to a PPC OS X 10.4
machine. It seems to work on sage.math and on my Intel OS X 10.5 box.
John
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
