Not selected yet, but probably the MIT license or some other permissive free license, unless Jeremy objects.
It sounds that you're quite far already - I'm super eager to take a
look at reticulated. On a side-note, what's the license of
On Fri, Mar 22, 2013 at 6:54 PM, Michael M. Vitousek
> (Thanks for forwarding Shashank, I wasn't on the list but I am now!)
> Hi Darjus,
> We're definitely happy to talk about where we are right now. In the last few
> months I've been working on a pure Python tool, called Reticulated, that
> typechecks gradually-typed Python programs and inserts casts between
> statically-typed and dynamically-typed parts of code. This is designed to be
> complimentary to the existing gradual module (though they haven't been
> integrated yet): Reticulated looks at code statically (as an AST) and
> inserts casts into the program based on annotated types Those casts can be
> calls into the gradual module which ensure that values flowing from dynamic
> code to static code have the expected type.
> I'm also hoping that Reticulated could be useful for more specialized tasks
> as well -- the casts it inserts don't necessarily have to be calls into the
> gradual module, but could also be calls into other libraries as well.
> At the moment, Reticulated only supports 3.2 and 3.3, so one of my highest
> priorities (based on conversations at PyCon and with Jim) is to port it to
> 2.7 (which shouldn't be too difficult).
> This project is currently in a private repo but I'm planning to move it to a
> public github repo ASAP. At the moment we're a little busy because we're
> working rather frantically on a paper to submit to OOPSLA on Thursday, but
> I'll do my best to bring it out into the open as soon as I can and I'll post
> again when I've done so.
> Michael Vitousek
> On Fri, Mar 22, 2013 at 7:20 PM, Darjus Loktevic <firstname.lastname@example.org> wrote:
>> Awesome! I'd love to know more about the progress, remaining
>> issues/todo list, future/feature plans, etc.
>> On Fri, Mar 22, 2013 at 10:25 AM, Shashank Bharadwaj
>> <email@example.com> wrote:
>> > (cc'ing Michael and Jeremy, I don't know if they are on jython-dev)
>> > Hi Darjus,
>> > Thanks for starting the conversation. The fork of Jython with gradual
>> > typing
>> > lives here: https://bitbucket.org/shashank/jython-gradual
>> > We have an experimental repository with a pure Python implementation of
>> > the
>> > runtime semantics of gradual typing at
>> > https://bitbucket.org/gradual/py-gradual
>> > There hasn't been any much progress on both of these for the last couple
>> > of
>> > months (since late Nov 2012 actually).
>> > I will let Michael talk about what he has been working over the few
>> > months.
>> > On Thu, Mar 21, 2013 at 11:36 PM, Darjus Loktevic <firstname.lastname@example.org>
>> > wrote:
>> >> First of all, sorry for hijacking the mailing list (it's somewhat
>> >> related to Jython)...
>> >> Jim, Shashank, Michael,
>> >> I hope all of you guys are on this list :) - This is a followup to our
>> >> chat at PyCon.
>> >> I found a paper from you guys called "Towards Gradual Typing in
>> >> Jython", interesting stuff.
>> >> I would love to get even more information about gradual: code
>> >> location, status, future plans, etc. Can you share some of this info?
>> >> Cheers!
>> >> Darjus
>> >> ------------------------------------------------------------------------------
>> >> Everyone hates slow websites. So do we.
>> >> Make your web apps faster with AppDynamics
>> >> Download AppDynamics Lite for free today:
>> >> http://p.sf.net/sfu/appdyn_d2d_mar
>> >> _______________________________________________
>> >> Jython-dev mailing list
>> >> Jythonemail@example.com
>> >> https://lists.sourceforge.net/lists/listinfo/jython-dev
>> > --
>> > Shashank Bharadwaj