Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Spike on environment activation with poetry #4235

Closed
qubitron opened this issue Jan 31, 2019 · 3 comments
Closed

Spike on environment activation with poetry #4235

qubitron opened this issue Jan 31, 2019 · 3 comments
Labels
area-environments Features relating to handling interpreter environments feature-request Request for new features or functionality
Milestone
2019, week 5 - Ja...

Comments

@qubitron
Copy link

qubitron commented Jan 31, 2019 •
edited by DonJayamanne
Loading

Note:

Activating poetry environments don't work.
python-poetry/poetry#198
python-poetry/poetry#571
@ghost ghost added the triage-needed Needs assignment to the proper sub-team label Jan 31, 2019
@ericsnowcurrently ericsnowcurrently self-assigned this Jan 31, 2019
@d3r3kk d3r3kk added the triage label Jan 31, 2019
@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Jan 31, 2019
@luabud
Copy link
Member

luabud commented Feb 12, 2019

Outcome

Understand how poetry does:

  • Creation/activation of environments
  • Installation of third-party tools

@luabud luabud added needs proposal Need to make some design decisions and removed triage labels Feb 12, 2019
@DonJayamanne DonJayamanne changed the title Spike on poetry Spike on environment activation with poetry Feb 27, 2019
@brettcannon brettcannon added feature-interpreter feature-request Request for new features or functionality labels Jun 3, 2019
@DonJayamanne DonJayamanne mentioned this issue Oct 3, 2019
Closed
@gramster gramster added area-environments Features relating to handling interpreter environments and removed area-environments Features relating to handling interpreter environments feature-interpreter labels Oct 10, 2019
@bruceadams
Copy link

Looks like #8372 is related to this.

@luabud luabud added needs spike Label for issues that need investigation before they can be worked on. and removed needs proposal Need to make some design decisions labels Mar 12, 2020
@luabud
Copy link
Member

luabud commented Apr 20, 2020

Thanks @bruceadams! Closing in favour of #8372.

@luabud luabud closed this as completed Apr 20, 2020
@ghost ghost removed the needs spike Label for issues that need investigation before they can be worked on. label Apr 20, 2020
@lock lock bot locked as resolved and limited conversation to collaborators May 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area-environments Features relating to handling interpreter environments feature-request Request for new features or functionality
Projects
None yet
Milestone
2019, week 5 - Jan Sprint 3
Development

No branches or pull requests
8 participants
@brettcannon @bruceadams @ericsnowcurrently @DonJayamanne @gramster @d3r3kk @qubitron @luabud