#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:26 jdemeyer]:
> Replying to [comment:16 leif]:
> > I was always against resolving all symbolic links in `SAGE_ROOT`, but
Jeroen decided to do so
> That is absolutely untrue. You're probably refering to #5852, but that
was about ''fixing'' the way ''how'' `sage` resolves symbolic links. I
never made the decision to resolve all symbolic links in `SAGE_ROOT`.
Well, we used `realpath()` and the like in a few places (mostly to check
whether two filenames actually refer to the same file), but never fully
"expanded" `SAGE_ROOT` "from the beginning", i.e., in the main `sage`
script. I recall you implemented the latter, so it's IMHO fair to say (or
assume) you were in favour of doing so...
Since then, nearly no Sage component ever sees what the user specified (or
is willing to use), hence presents the user only and always the fully
dereferenced form, which is certainly annoying to a couple of people (and
also causes some technical trouble, as mentioned earlier).
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13928#comment:27>
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.
