#13928: Problematic file filter in skip() from sage-ptest
---------------------------------+------------------------------------------
Reporter: ncohen | Owner: mvngu
Type: defect | Status: needs_review
Priority: major | Milestone: sage-5.6
Component: doctest | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Nathann Cohen | Merged in:
Dependencies: | Stopgaps:
---------------------------------+------------------------------------------
Comment (by leif):
Replying to [comment:17 jhpalmieri]:
> Replying to [comment:15 leif]:
> > Replying to [comment:13 ncohen]:
>
> > > Then what's the problem with filtering the `/.` that appear in
SAGE_ROOT ?
> >
> > I'm not sure what you mean by that. Of course RCSs' directories can
be located anywhere, not just below `SAGE_ROOT`, and even for the latter
aren't necessarily [just] Mercurial's `.hg` directories.
>
> I think he means, what's wrong with just filtering subdirectories of
`SAGE_ROOT` (and its subdirectories) which start with `.`? This would be
consistent with Nils' suggestion.
Well, I'd say it's even ''more likely'' that the tree(s) contain(s) (e.g.)
`.svn` or `.git` directories if someone tests files ''outside''
`SAGE_ROOT`. Feeding `sage -t ...` with complex {{{`find ... -prune
...`}}} expressions is certainly pretty inconvenient.
We could of course introduce yet another Sage environment variable
containing the directory names to skip... ;-)
[and only skip them if they're really ''below'' the directories specified,
as Nils suggested.]
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13928#comment:20>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
