pyvo Move astropy.samp to pyvo

Did we discuss this at IVOA Interop? cc @astrofrog

Jun 21 '19 01:06 pllim

We didn't really discuss it, but it's certainly an option! (I'd argue that other things like VOTable belong in the core package, but no strong opinions on astropy.samp)

Jun 21 '19 09:06 astrofrog

I also agree that votable should stay in the core since it is very much integrated with the unified I/O.

Jun 21 '19 12:06 pllim

This would also require to de-couple the submodules from the top-module. (It's not necessary to import the whole dal stack for just broadcasting a table.)

Jun 21 '19 13:06 funbaker

At Astropy Coordination Meeting 2019, this was decided to be a good idea. But io.votable would stay in astropy.

Dec 12 '19 16:12 pllim

Is there a roadmap for this?

Jun 17 '20 16:06 pllim

Renewing this effort...

The goal: We would like to deprecate then removeastropy.samp from astropy in favor of SAMP capabilities in pyvo.

Note that pyvo/samp depends on astropy.samp, so that reference will need to change. This work should ensure that existing pyvo SAMP capabilities are retained and that astropy SAMP capabilities are supported and documented.

For more details on this see the notes from unmerged PR #239.

Sep 22 '22 22:09 tomdonaldson

Please cross link the new PR here when you have one. Thank you so much! 🙏

Sep 26 '22 19:09 pllim

I'm removing the milestone from this one as this is not a thing that should block the 1.5 version.

Apr 12 '23 21:04 bsipocz