Replaced all instances of 'python' with 'python2'

[sudonym1]

On systems where 'python' refers to python3, redo
failed to launch. All invocations of python have been
made explicitly python2 invocations. All tests pass
on an Arch Linux system as of this commit.

[apenwarr]

Yeah, okay. I guess it's time for that :)

[tgs]

Thanks for this! It also helps when running redo while a python 3 virtualenv is activated.

You missed one though - redo-log still has just python

[sudonym1]

Hmm. The unit tests passed. I will take a look tonight. Maybe a new unit test is needed.

…

Sent from my iPhone

On Nov 20, 2018, at 10:50 AM, Thomas Smith ***@***.***> wrote: Thanks for this! It also helps when running redo while a python 3 virtualenv is activated. You missed one though - redo-log still has just python — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[apenwarr]

redo-log hadn't been merged at the time you made your patch, and I missed it when combining the two. I'll add it :) On Tue, Nov 20, 2018 at 2:35 PM Seamus Connor <notifications@github.com> wrote:

…

Hmm. The unit tests passed. I will take a look tonight. Maybe a new unit test is needed. Sent from my iPhone > On Nov 20, 2018, at 10:50 AM, Thomas Smith ***@***.***> wrote: > > Thanks for this! It also helps when running redo while a python 3 virtualenv is activated. > > You missed one though - redo-log still has just python > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub, or mute the thread. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#22 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABQcHicjbKdMYV_AjgsIpyMJsjai5M8ks5uxFl4gaJpZM4YeXfQ> .

[apenwarr]

...and I've pushed a fix to master.

…

On Tue, Nov 20, 2018 at 2:43 PM Avery Pennarun ***@***.***> wrote: redo-log hadn't been merged at the time you made your patch, and I missed it when combining the two. I'll add it :) On Tue, Nov 20, 2018 at 2:35 PM Seamus Connor ***@***.***> wrote: > Hmm. The unit tests passed. I will take a look tonight. Maybe a new unit > test is needed. > > Sent from my iPhone > > > On Nov 20, 2018, at 10:50 AM, Thomas Smith ***@***.***> > wrote: > > > > Thanks for this! It also helps when running redo while a python 3 > virtualenv is activated. > > > > You missed one though - redo-log still has just python > > > > — > > You are receiving this because you authored the thread. > > Reply to this email directly, view it on GitHub, or mute the thread. > > — > You are receiving this because you modified the open/close state. > Reply to this email directly, view it on GitHub > <#22 (comment)>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AABQcHicjbKdMYV_AjgsIpyMJsjai5M8ks5uxFl4gaJpZM4YeXfQ> > . >

[sudonym1]

Ahh, thanks.

…

Sent from my iPhone

On Nov 20, 2018, at 11:43 AM, apenwarr ***@***.***> wrote: redo-log hadn't been merged at the time you made your patch, and I missed it when combining the two. I'll add it :) On Tue, Nov 20, 2018 at 2:35 PM Seamus Connor ***@***.***> wrote: > Hmm. The unit tests passed. I will take a look tonight. Maybe a new unit > test is needed. > > Sent from my iPhone > > > On Nov 20, 2018, at 10:50 AM, Thomas Smith ***@***.***> > wrote: > > > > Thanks for this! It also helps when running redo while a python 3 > virtualenv is activated. > > > > You missed one though - redo-log still has just python > > > > — > > You are receiving this because you authored the thread. > > Reply to this email directly, view it on GitHub, or mute the thread. > > — > You are receiving this because you modified the open/close state. > Reply to this email directly, view it on GitHub > <#22 (comment)>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AABQcHicjbKdMYV_AjgsIpyMJsjai5M8ks5uxFl4gaJpZM4YeXfQ> > . > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[tgs]

Thank you! :) On Tue, Nov 20, 2018 at 4:51 PM Seamus Connor <notifications@github.com> wrote:

…

Ahh, thanks. Sent from my iPhone > On Nov 20, 2018, at 11:43 AM, apenwarr ***@***.***> wrote: > > redo-log hadn't been merged at the time you made your patch, and I missed > it when combining the two. I'll add it :) > > On Tue, Nov 20, 2018 at 2:35 PM Seamus Connor ***@***.***> > wrote: > > > Hmm. The unit tests passed. I will take a look tonight. Maybe a new unit > > test is needed. > > > > Sent from my iPhone > > > > > On Nov 20, 2018, at 10:50 AM, Thomas Smith ***@***.*** > > > wrote: > > > > > > Thanks for this! It also helps when running redo while a python 3 > > virtualenv is activated. > > > > > > You missed one though - redo-log still has just python > > > > > > — > > > You are receiving this because you authored the thread. > > > Reply to this email directly, view it on GitHub, or mute the thread. > > > > — > > You are receiving this because you modified the open/close state. > > Reply to this email directly, view it on GitHub > > <#22 (comment)>, or mute > > the thread > > < https://github.com/notifications/unsubscribe-auth/AABQcHicjbKdMYV_AjgsIpyMJsjai5M8ks5uxFl4gaJpZM4YeXfQ > > > . > > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub, or mute the thread. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#22 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAOAfmJM7SVtMQdsuIy03XbgWvtyN_CEks5uxHlqgaJpZM4YeXfQ> .