Re: [PATCH] ob-python: Rename exec tmpfile handle to prevent conflict

Bastien writes: > Hi Jack, > > Jack Kamm writes: > >> Thanks Bastien, the Woof! tool looks interesting. > > Thanks! I'm working on a small woof.el package to make it more > useful for both maintainers (setting headers) and users (checking > upcoming changes or help requests). > This is

Re: [PATCH] ob-python: Rename exec tmpfile handle to prevent conflict

Hi Jack, Jack Kamm writes: > Thanks Bastien, the Woof! tool looks interesting. Thanks! I'm working on a small woof.el package to make it more useful for both maintainers (setting headers) and users (checking upcoming changes or help requests). > By the way, on seeing this thread again, I

Re: [PATCH] ob-python: Rename exec tmpfile handle to prevent conflict

Thanks Bastien, the Woof! tool looks interesting. By the way, on seeing this thread again, I realized this patch probably should have been applied to the maint branch. So I've cherry picked it into there, and merged back into master. Bastien writes: > Hi Jack and Adrian, > > Jack Kamm

Re: [PATCH] ob-python: Rename exec tmpfile handle to prevent conflict

Hi Jack and Adrian, Jack Kamm writes: > Adrian Kummerländer writes: > >> I noticed that after updating to Org 9.4 many of my Python-based Org >> files fail to execute with various `io.TextIOWrapper' related error >> messages. The reason for this is that opening the exec tmpfile as `f' >>

Re: [PATCH] ob-python: Rename exec tmpfile handle to prevent conflict

Hi Adrian, Adrian Kummerländer writes: > I noticed that after updating to Org 9.4 many of my Python-based Org > files fail to execute with various `io.TextIOWrapper' related error > messages. The reason for this is that opening the exec tmpfile as `f' > shadows this possibly user-defined