Skip to content

Optional dependency checker tool #63

Closed

Description

@mdboom

At the Boston meeting, it was discussed that there would be a tool to check for optional dependencies, list the versions that were found and, where possible, install them. I'm assigning @eteq, because I believe he already has a similar tool in Astropysics.

Activity

  1. ghost assigned on Nov 11, 2011
  2. mdboom commented on Nov 11, 2011

    @mdboom
    ContributorAuthor

    astropy.io.vo has an optional dependency on xmllint (through the shell -- it is a C command line application).

  3. eteq commented on Nov 11, 2011

    @eteq
    Member

    Yep, this is third on my to-do list after the config and a docs cleanup - It'll also tie pretty closely with the affiliated package index (as they will also certainly have optional deps). In the meantime, lets use this issue to keep track of optional dependencies.

    astropy op deps:

    • scipy
    • matplotlib

    testing op deps:

    • py.test
    • pep8
    • pytest-pep8
    • coverage
    • pytest-coverage
  4. eteq commented on Jun 13, 2012

    @eteq
    Member

    This was originally intended for 0.1, but it looks like it will need to be triaged for 0.2. Note that part of this is ongoing at https://github.com/eteq/astropy/tree/dependencies

  5. wkerzendorf commented on Dec 14, 2012

    @wkerzendorf
    Member

    @iguananaut: I marked the #476 PR as 0.2 milestone (tentatively). Can this issue then be closed?

  6. embray commented on Dec 14, 2012

    @embray
    Member

    Hm. Let's leave it open for now since #476 is just one possible implementation of this. I'm pretty confident it's what we'll end up going with but I see this as still an "open issue" until some specific solution is merged.

  7. astrofrog commented on Jan 20, 2013

    @astrofrog
    Member

    I'm re-scheduling this as 0.2.1 since I also re-scheduled #476.

  8. astrofrog commented on Sep 20, 2013

    @astrofrog
    Member

    Re-scheduling this for 0.4.0 - I don't think it's important enough to worry about for now

  9. modified the milestones: v1.0.0, v0.4.0 on May 3, 2014
  10. eteq commented on Jun 5, 2014

    @eteq
    Member

    Closing a la discussion in #476

  11. modified the milestones: Future, v1.0.0 on Jun 6, 2014
  12. added a commit that references this issue on Nov 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions