Skip to content

Update installation documentation  #6154

Closed

Description

@mwcraig

One suggestion made in #6051 was to update the installation section of the documentation to focus on anaconda for new users; see #6051 (comment) for the one idea for doing that. It was clear this topic needed more discussion, so was dropped in #6051.

The purpose of this issue is to remind to update the installation documentation at some point..

Activity

  1. added this to the v2.0.0 milestone on Jun 4, 2017
  2. pllim commented on Jun 15, 2017

    @pllim
    Member

    I doubt anyone is going to get this done by tomorrow, so removing milestone.

  3. removed this from the v2.0.0 milestone on Jun 15, 2017
  4. bsipocz commented on Jun 15, 2017

    @bsipocz
    Member

    @pllim - docs and bugfixes can be backported before the actual release.

  5. bsipocz commented on Jun 30, 2017

    @bsipocz
    Member

    This is actually a duplication of #1807, but I go ahead and close that one as it's burried under tons of other issues.

  6. KING-SID commented on Feb 3, 2019

    @KING-SID

    Hey! I am new to the astropy developers community and open source. Given that this issue is still open, I'd like to take a crack at it as I recently went through the installation docs myself just recently and faced the issue first hand. I can offer the first time installer perspective on this issue. I've been told how I can work on this, getting straight to it!

  7. kakirastern commented on Feb 5, 2019

    @kakirastern
    Contributor

    Hi @KING-SID, I have opened a PR #8385 to address this issue regarding the development workflow parts... Maybe this issue is overlapping with Issue #7287 as well as Issue #8289, as the installation with Python 2.x is being phased out and Python 3.x is now the default version?

  8. kakirastern commented on Feb 5, 2019

    @kakirastern
    Contributor

    @KING-SID So a PR can be opened that deals with installation issues in other areas of the AstroPy website, as long as it is not part of development workflow... at least for now, as I am working on it.

  9. 4 remaining items

  10. KING-SID commented on Feb 6, 2019

    @KING-SID

    @bsipocz Thanks for the heads up!

  11. kakirastern commented on Mar 9, 2019

    @kakirastern
    Contributor

    Hi, can I help by updating the installation docs as suggested in #6051 (comment)?

  12. CosmicTiger commented on Oct 21, 2020

    @CosmicTiger

    Assign to me this issue. I'll work on it.

  13. embray commented on Apr 22, 2021

    @embray
    Member

    The installation page for SciPy is nice and pretty succinct: http://scipy.github.io/devdocs/getting_started.html One thing I might do is emphasizing venv as an option when using pip, or pip install --user. Not sure.

  14. SauravMaheshkar commented on Dec 14, 2021

    @SauravMaheshkar

    Should this issue still be open ?

  15. mwcraig commented on Dec 14, 2021

    @mwcraig
    MemberAuthor

    I think it should still be open since #10919 was never merged. Will try to take a look on Thursday.

  16. exitflynn commented on Jan 6, 2023

    @exitflynn

    HI there! So... should the issue still be open? :P

  17. astrojuanlu commented on Jan 6, 2023

    @astrojuanlu
    Member

    Been almost 6 years since opening the issue. Is the stance of the project still that conda should come first? In #10919 there was some debate about it. If it has to be done, essentially #10919 should be repeated. If not, this issue should be closed IMO.

  18. pllim commented on Jan 23, 2023

    @pllim
    Member

    Hah, I really don't want another debate on pip vs conda... I'll slap a "Close?" label on this issue and see what happens. Thanks for the ping. 😉

  19. added
    Close?Tell stale bot that this issue/PR is stale
    on Jan 23, 2023
  20. github-actions commented on Jan 24, 2023

    @github-actions
    Contributor

    Hi humans 👋 - this issue was labeled as Close? approximately 13 hours ago. If you think this issue should not be closed, a maintainer should remove the Close? label - otherwise, I will close this issue in 7 days.

    If you believe I commented on this issue incorrectly, please report this here

  21. mwcraig commented on Jan 24, 2023

    @mwcraig
    MemberAuthor

    I think it is fine to close -- happily, binary distributions are much more widely available now outside of conda.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions