Hi Ben, Great idea. At the moment I see:
~/antlr/code/antlr/main/runtime $ ls */dist C/dist: libantlr3c-3.0.1.tar.gz libantlr3c-3.1.tar.gz libantlr3c-3.1.1b1.tar.gz Python/dist: antlr_python_runtime-3.1-py2.4.egg antlr_python_runtime-3.1.tar.gz antlr_python_runtime-3.1-py2.5.egg antlr_python_runtime-3.1.zip Should just add an scp for any target that has that in their runtime dir? Johannes, you could add that right too? Ter On Aug 14, 2008, at 10:24 AM, Benjamin Niemann wrote: > Hi Ter, > > no need to wait. It's in perforce in the dist/ dir of the python > target. > (I was assuming, you remembered that from the last release. Perhaps we > can make this a convention and you can update your release script to > upload the contents of the /runtime/[target]/dist/ when present.) > > -Ben > > On Thu, Aug 14, 2008 at 1:33 AM, Terence Parr <[EMAIL PROTECTED]> > wrote: >> Yes, grab main distribution and you'll get it... just waiting to >> get in the >> binary from Benjamin to put there. >> Ter >> On Aug 13, 2008, at 3:42 PM, Simos Xenitellis wrote: >> >>> Hi, >>> >>> The URL http://antlr.org/download/Python/ >>> shows vesion 3.0.1 while 3.1 appears to be available. >>> >>> Is 3.1 ready yet for use >>> (http://fisheye2.atlassian.com/browse/antlr/runtime/Python)? >>> >>> Simos >> >> _______________________________________________ antlr-dev mailing list [email protected] http://www.antlr.org:8080/mailman/listinfo/antlr-dev
