#18748: Python library to bootstrap Sage
-------------------------------------+-------------------------------------
       Reporter:  vbraun             |        Owner:
           Type:  defect             |       Status:  needs_review
       Priority:  blocker            |    Milestone:  sage-6.8
      Component:  build              |   Resolution:
       Keywords:                     |    Merged in:
        Authors:  Volker Braun       |    Reviewers:
Report Upstream:  N/A                |  Work issues:
         Branch:                     |       Commit:
  u/vbraun/python_library_to_bootstrap_sage|  
e45a0b667f908f147cabbec63fe88134061ac69a
   Dependencies:                     |     Stopgaps:
-------------------------------------+-------------------------------------

Comment (by jdemeyer):

 Replying to [comment:31 vbraun]:
 > And moving stuff is super-easy in git, its a matter of minutes.
 Moving the files physically, sure. But that's only a very small part of
 the effort of moving files. All the code referring to those files needs to
 be changed, everything has to be tested again...

 > So why do it now when /build is not ready for it?
 First of all, I don't agree with the premise that "`build` is not ready
 for it". I really don't see the problem. Second, like I already said: I
 would avoid having to move things in the future.

--
Ticket URL: <http://trac.sagemath.org/ticket/18748#comment:35>
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 http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to