(ie. I'd hope it doesn't get blocked indefinitely on "cleaning") On May 24, 2013 9:44 AM, "Greg Stein" <gst...@gmail.com> wrote:
> Please commit first, then clean. > On May 24, 2013 6:23 AM, "Jim Jagielski" <j...@jagunet.com> wrote: > >> Yeah, I should commit my script (which is Python, btw) that does >> the correlation between the Emails rec'd as monitor and the >> final tally report. What it does is check that each vote in >> the tally matches what was rec'd in email. and that each vote >> sent in an email is represented in the tally ;) >> >> Need to clean it up a little though... >> >> On May 24, 2013, at 1:31 AM, Alan Cabrera <l...@toolazydogs.com> wrote: >> >> > Python FTW! >> > >> > I ran into some bits that broke down for me when I monitored the vote >> today. I'll fix those right away. >> > >> > I thought that I could write some semi-automatic tooling and better >> documentation for monitors as well. This will have to wait until I'm done >> with some Incubator tooling that I committed to doing; it was waiting on >> some LinkedIn code that I now have approval to copy over. I'm guessing >> June-ish is when I can work on Steve python tooling. >> > >> > >> > Regards, >> > Alan >> > >> > >> > On May 23, 2013, at 2:42 PM, ke...@apache.org wrote: >> > >> >> Python +1999999. >> >> >> >> --k >> >> >> >> On 2013.May.23, at 4.28p, Jim Jagielski <j...@jagunet.com> wrote: >> >> >> >>> To replace the Perl stuff? Or updates to the current >> >>> Python scripts? >> >>> >> >>> Either way: +1! >> >>> On May 23, 2013, at 2:15 PM, Alan Cabrera <l...@toolazydogs.com> >> wrote: >> >>> >> >>>> I just used the Steve tooling today and I will work on sprucing up >> Python versions. >> >>>> >> >>>> >> >>>> Regards, >> >>>> Alan >> >>>> >> >>> >> >> >> > >> >>
