#378: User-specified path for load and attach
--------------------------------------------+-------------------------------
Reporter: was | Owner: was
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-4.6.1
Component: user interface | Keywords:
Author: Mitesh Patel, Felix Lawrence | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
--------------------------------------------+-------------------------------
Changes (by newvalueoldvalue):
* author: Mitesh Patel => Mitesh Patel, Felix Lawrence
Comment:
Replying to [comment:21 jsrn]:
> My only comment on the current patch, is that maybe there should be a
TODO (or a fix ;-) ) in reset_load_attach_path(), which notes that
probably the elements of SAGE_LOAD_ATTACH_PATH should be uniquified while
preserving the order (thus, list(set(_load_attach_path)) is no good).
After that the while could be reverted to an if again when removing the
empty element.
Do we really need to test for uniqueness at all? It's the user's fault if
they get it wrong, and the only negative consequence I see is that
attaching/loading files (not the sort of operation that sits deep in a
loop) a tiny tiny bit slower. Python doesn't check for uniqueness in
sys.path, BASH doesn't check for uniqueness in $PATH. AFAIK the main
argument for uniqueness is aesthetics; perhaps we can leave this to the
user rather than try to tidy up after them (and perhaps do something
unexpected in the process)?
Replying to [comment:22 mpatel]:
>One question that may relate to how/whether we "expose" the path list:
Would users want Sage to search some paths recursively for files to load
or attach? How would we store this information?
This is an interesting question. I think it would be a nice feature.
Since we don't actually expose the path array, it would be easy to add
such features later, so it's probably best as a new ticket.
I also noticed that I was fat-fingered typing the name of the new patch -
387 instead of 378. *sigh*
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/378#comment:23>
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.
