Hi So I'm getting to the point in my masters thesis where I have coded some different .sage files and now I have to package it in some way making it easy to use with SAGE for my professor and the censor.
I just want to explain the content of my implementation in short: It is basically a slow pairing based signature system (BLS). signature_scheme.sage file which uses some of the different components in sage: field_ext, elliptic_curves etc. And then it also uses a weil pairing function I've written in sage, I do not want to make this part of the signature scheme code, since if I have some extra time later I want to work on trying to make this function faster (haven't really figured out how) I'm currently in the process of wrapping the functions in my signature_cheme.sage file in a signature_scheme class providing a static scheme setup and maybe making it possible to generate a interact in notebook() mode. I've looked at making a .spkg but I'm not really sure that this is the correct thing to do, since I want to call components in SAGE and all the optional packages I've looked at is mostly just code ported from c by wrapping with some python setup files (I haven't looked at all the packages). I guess what I am asking is: Is making a spkg from my sage code, the right thing to do or is it complete nonsense? Since I've yet only encountered spkg's made from external code bases. If there is a counter example of this, then please let me know, then I can use it as a template if I were to package my code. --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
