Why is tp2vis written as a script?

[keflavich]

As currently written, tp2vis can't be imported by other modules and can't be used as a library, since instead of importing, users are expected to execfile it. Is there a python3/casa6-compatible, importable version available? It looks like the fix is as simple as including appropriate imports (e.g., from taskinit import iatool, etc) at the top of the file.

[teuben]

we are aware of it, we developed it that way, and it is a bit clunky and non setup.py compliant. But given the casa eco-system which wasn't either (arguably) we just did it the clunky way. I am "working" on a casa6 version which would solve this issue. I don't recall is there was something else stopping me from doing that, or just finding the time :-( The parent github is still private, which is annoying for people like you who might like to contribute. I'll see if I can convince Jin, or perhaps he sees this message and replies.

…

On Thu, Nov 21, 2019 at 10:20 AM Adam Ginsburg ***@***.***> wrote: As currently written, tp2vis can't be imported by other modules and can't be used as a library, since instead of importing, users are expected to execfile it. Is there a python3/casa6-compatible, importable version available? It looks like the fix is as simple as including appropriate imports (e.g., from taskinit import iatool, etc) at the top of the file. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#3?email_source=notifications&email_token=AAZ4MGMTF5M5MO2CET6IOXLQU2RM5A5CNFSM4JQD5FK2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H3EHEOA>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZ4MGMNWZ5B7HTJ4PWVHATQU2RM5ANCNFSM4JQD5FKQ> .

[keflavich]

it's worse than not-setup.py-compliant, it really can't be used outside of an explicitly interactive context.

I have a partial (?) soln here: #4