Gonzalo, On Mon, Mar 15, 2010 at 1:17 PM, Gonzalo Tornaria <torna...@math.utexas.edu>wrote:
> On Mon, Mar 15, 2010 at 3:57 PM, Brian Granger <ellisonbg....@gmail.com> > wrote: > > Thanks for describing this better, it helps me to understand what the > > current _sig_on/_sig_off does. Because of the licensing issues, I am > > not looking at the code in Sage until it has been officially re-licensed. > > Once that has been done, I will dig into the code to see what it > actually > > does. > > Wow, you are serious about licensing. I don't think it would be a > problem for you t look at it --- everybody agreed to relicense > anyway... > > I suppose I am, especially with the GPL. Probably from my days in industry.... But, at a practical level I find that if I read someone's code before trying to implement it myself, it is almost impossible to not copy what they did - especially if it is something I don't understand it very well. I realize everyone has agreed to the re-license, but I feel it is a way of respecting people's contributions to wait until it has been re-licensed in the source ....also I don't merely want to read the code, I want to copy it, and start hacking :) >> PPS: this seems to be very "ingrained" with the sage inners for > >> library interfaces, and it's already in there, so it's hard to make a > >> list of reasons we want to use (e.g. issues we would have otherwise, > >> features we want it to support, etc). Since you are coming from a > >> different camp, maybe you can try to list your reasons -- what > >> problems do you think this would fix for you, and what enhancements > >> would this bring up. [ok, I know some reasons for sage, but I'm not > >> listing any to avoid biasing you... ] > >> > > > > I am not sure I am following what you are asking. Can you elaborate on > this > > question? > > Sorry. I'll rephrase: > > What are your reasons for needing this _sig_on/_sig_off stuff. What > problems do you have that you think this would fix for you, and what > enhancements you think this would this bring up. > > I have built Cython wrappers for a C library (www.zeromq.org). They are working wonderfully, but there is one particular call in the C API that can block indefinitely when things go wrong. In that case, I currently cannot SIGINT the code to stop the program (I have to kill -9 it in a different terminal). Thus, if I put _sig_on/_sig_off around that call, I will be able to do ctrl-C. In my case, nesting is not an issue, but Windows support is. Cheers, Brian > It will be helpful to have the perspective of somebody outside of sage. > > Gonzalo > > -- > To post to this group, send an email to sage-devel@googlegroups.com > To unsubscribe from this group, send an email to > sage-devel+unsubscr...@googlegroups.com<sage-devel%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/sage-devel > URL: http://www.sagemath.org > -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
