Skip to content

Move astropy.samp to pyvo #155

Closed
Closed

Description

@pllim

Did we discuss this at IVOA Interop? cc @astrofrog

Activity

  1. astrofrog commented on Jun 21, 2019

    @astrofrog
    Member

    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)

  2. pllim commented on Jun 21, 2019

    @pllim
    MemberAuthor

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

  3. funbaker commented on Jun 21, 2019

    @funbaker
    Contributor

    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.)

  4. pllim commented on Dec 12, 2019

    @pllim
    MemberAuthor

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

  5. changed the title [-]Move astropy.samp to pyvo?[/-] [+]Move astropy.samp to pyvo[/+] on Dec 12, 2019
  6. pllim commented on Jun 17, 2020

    @pllim
    MemberAuthor

    Is there a roadmap for this?

  7. self-assigned this
    on Sep 22, 2022
  8. tomdonaldson commented on Sep 22, 2022

    @tomdonaldson
    Contributor

    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.

  9. added this to the v1.5 milestone on Sep 22, 2022
  10. pllim commented on Sep 26, 2022

    @pllim
    MemberAuthor

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

  11. bsipocz commented on Apr 12, 2023

    @bsipocz
    Member

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

  12. removed this from the v1.5 milestone on Apr 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions