Skip to content

[meta] Use conda run for running tools #7425

Closed

Description

@luabud
No description provided.

Activity

  1. ghost removed
    triage-neededNeeds assignment to the proper sub-team
    on Sep 16, 2019
  2. luabud commented on Sep 16, 2019

    @luabud
    MemberAuthor
  3. changed the title [-]Use conda run for running tools[/-] [+]Use `conda run` for running tools[/+] on Sep 16, 2019
  4. DonJayamanne commented on Sep 17, 2019

    @DonJayamanne

    Isn't this a duplicate of #6010?

  5. luabud commented on Sep 17, 2019

    @luabud
    MemberAuthor

    Don Jayamanne (@DonJayamanne) we separated the issues for running tools and for the debugger

  6. DonJayamanne commented on Sep 17, 2019

    @DonJayamanne

    Added another item for running Jupyter (DataScience)

  7. DonJayamanne commented on Sep 17, 2019

    @DonJayamanne

    Luciana Abud (@luabud) Brett Cannon (@brettcannon)
    I'd prefer to somehow implement this as an experiment.
    I.e. roll this out slowly to users, rather than everyone in one go. This way we'll know whether it works or not. If it doesn't work or we have issues, then the number of users impacted is small.

  8. brettcannon commented on Sep 18, 2019

    @brettcannon
    Member

    Don Jayamanne (@DonJayamanne) how is this not going to be an improvement from what we are doing now? conda run is the official way to do this sort of thing now, so I'm not seeing where the worry is about it being "wrong".

  9. DonJayamanne commented on Sep 19, 2019

    @DonJayamanne

    I'm not seeing where the worry is about it being "wrong".

    Just a fear of something going wrong. Nothing else. 😁

  10. karrtikr commented on Sep 25, 2019

    @karrtikr

    Meta issue

  11. changed the title [-]Use `conda run` for running tools[/-] [+][meta] Use `conda run` for running tools[/+] on Sep 25, 2019
  12. ericsnowcurrently commented on Sep 30, 2019

    @ericsnowcurrently

    There is also a concern that "pythonPath" in debug config (see #7690) can conflict and cause a problem.

  13. luabud commented on Oct 9, 2019

    @luabud
    MemberAuthor

    Closing in favour of #5344.

  14. ghost removed on Oct 9, 2019
  15. locked as resolved and limited conversation to collaborators on Oct 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    debtCode quality issuesimportantIssue identified as high-prioritymetaIssue that is tracking an overall project

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions