#14482: create the new development scripts/library
-------------------------------------------------+-------------------------
       Reporter:  ohanar                         |        Owner:  jason
           Type:  task                           |       Status:  new
       Priority:  major                          |    Milestone:  sage-6.0
      Component:  misc                           |   Resolution:
       Keywords:  sd51                           |    Merged in:
        Authors:  Robert Bradshaw, David Roe,    |    Reviewers:
  Julian Rueth, R. Andrew Ohana, Martin Raum,    |  Work issues:
  Timo Kluck                                     |       Commit:
Report Upstream:  N/A                            |     Stopgaps:
         Branch:  u/saraedum/ticket/14482        |
   Dependencies:  #13015, #14480, #14557         |
-------------------------------------------------+-------------------------

Comment (by vbraun):

 Also, I'm not entirely happy with the git interface. Though I also think
 its good enough to use in the git scripts and its probably a bad idea to
 do any architectural changes at this point. For the record I've built on
 the current code at
 https://github.com/vbraun/SageUI/tree/release/src/sageui/model. Changes
 incude

 * Use proxy objects instead of having to import magic constants:
   {{{
 In [3]: git.status()   # return stdout by default, the most desirable
 behaviour
 Out[3]: '# On branch dev_scripts\nnothing to commit, working directory
 clean\n'

 In [4]: git.exit_code.status()
 Out[4]: 0

 In [5]: git.silent.status()

 In [6]: git.echo.status()
 # On branch dev_scripts
 nothing to commit, working directory clean
   }}}
 * Don't hardcode the Sage repo directory, this is probably going to be
 useful elsewhere
 * Use the `GIT_DIR` and `GIT_WORK_TREE` environment variables instead of
 `--git-dir` (though warning: there seems to be a bug in `git status`, it
 is not respecting `GIT_WORK_TREE`)
 * Split the git interface (handling the mechanics of interfacing with the
 git binary) from the logical repository handling (like the `create_ticket`
 method)
 * Put all the doctesting setup into a utility class instead of having
 lengthy sections creating `Doctest*` classes and sample repos.

--
Ticket URL: <http://trac.sagemath.org/ticket/14482#comment:32>
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/groups/opt_out.

Reply via email to