#20382: Replace is_package_installed with Features
-------------------------------------+-------------------------------------
       Reporter:  saraedum           |        Owner:
           Type:  enhancement        |       Status:  new
       Priority:  major              |    Milestone:  sage-7.2
      Component:  build              |   Resolution:
       Keywords:                     |    Merged in:
        Authors:  Julian Rüth        |    Reviewers:  Nicolas M. Thiéry,
Report Upstream:  N/A                |  ...
         Branch:                     |  Work issues:  reorder classes in
  u/saraedum/replace_is_package_installed_with_features|  sage.misc.feature
   Dependencies:                     |       Commit:
                                     |  2007e1822e0684078323677211c3a893d5af414e
                                     |     Stopgaps:
-------------------------------------+-------------------------------------

Comment (by saraedum):

 I already thought about moving parts of this out of the source tree. I
 have not really reached a conclusion yet. It certainly needs to be used
 during build time. Currently, we have `sage_setup/optional_extension.py`
 which calls `sage.misc.package.is_package_installed`. So, at least in a
 first version, I would certainly mimic this behaviour and check for a
 feature (in this case, whether Cython can build against a library) at
 build time.

 Replying to [comment:28 vdelecroix]:
 > This code is mostly Sage agnostic right?
 The idea is Sage agnostic. The features it checks for are of course
 relatively Sage specific.

 > Would it be possible to move this code out of Sage source code? It would
 better be in `sage/src/sage_setup/` or whatever appropriate (even possibly
 an external python module). We might want to use it outside of Sage or
 before Sage is built to track possible dependencies.
 I am not sure about moving it to `sage_setup`. We need this at runtime.
 Can we (and should we?) access things in `sage_setup` at runtime?
 It is an interesting idea to make it a separate package. There seems to be
 no python package around which does anything similar. I would be happy to
 pursue such a path but would like to postpone this to a followup ticket.

--
Ticket URL: <http://trac.sagemath.org/ticket/20382#comment:30>
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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to