Figure out where things stand

[jyeatman]

We need to go through our various scripts, figure out what still works, and fix bugs
In other words: Identify the problem and fix it

[richford]

@jyeatman and @arokem: Seems like a stale issue (or one that could never be closed). Is it safe to close this one?

[jyeatman]

I agree that this issue is likely to remain relevant for the lives of our programming careers. In regards to pyAFQ we do need to identify the problem and fix it. But yes, not a helpful issue beyond reminding us where things stood at the end of 2016

[arokem]

Since this one is a perennial, I'm just going to go ahead and close it, so we can keep things neat around here. But we'll keep this in mind, for sure.

[jyeatman]

That seems reasonable

…

On Tue, Feb 26, 2019 at 4:23 PM Ariel Rokem ***@***.***> wrote: Since this one is a perennial, I'm just going to go ahead and close it, so we can keep things neat around here. But we'll keep this in mind, for sure. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#39 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABsYyjeKWgV0mqinJoIeRrwT5OMY5MKlks5vRc-mgaJpZM4LExes> .