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.

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

pip does not get correct flags in env for outputs #4157

Closed
beckermr opened this issue Dec 15, 2020 · 4 comments
Closed

pip does not get correct flags in env for outputs #4157

beckermr opened this issue Dec 15, 2020 · 4 comments
Labels
duplicate indicate issues/PRs that are duplicates of another locked [bot] locked due to inactivity stale::recovered [bot] recovered after being marked as stale

Comments

@beckermr
Copy link
Contributor

Actual Behavior

Expected Behavior

Steps to Reproduce

Output of conda info

It appears that pip is not getting flags like --no-deps when used in outputs. See this recipe: https://github.com/conda-forge/google-cloud-bigquery-storage-feedstock and this build: https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=238367&view=logs&j=656edd35-690f-5c53-9ba3-09c10d0bea97&t=e5c8ab1d-8ff9-5cae-b332-e15ae582ed2d

@github-actions
Copy link

Hi there, thank you for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.

If you would like this issue to remain open please:

  1. Verify that you can still reproduce the issue at hand
  2. Comment that the issue is still reproducible and include:
    - What OS and version you reproduced the issue on
    - What steps you followed to reproduce the issue

NOTE: If this issue was closed prematurely, please leave a comment.

Thanks!

@github-actions github-actions bot added the stale [bot] marked as stale due to inactivity label May 19, 2023
@beckermr
Copy link
Contributor Author

Not stale.

@github-actions github-actions bot added stale::recovered [bot] recovered after being marked as stale and removed stale [bot] marked as stale due to inactivity labels May 20, 2023
@jakirkham
Copy link
Member

Agree this is still an issue

Wonder if this is the same as issue ( #3993 )

@jaimergp jaimergp added the duplicate indicate issues/PRs that are duplicates of another label Mar 25, 2024
@jaimergp
Copy link
Contributor

Yes, I think it's a duplicate. Closing in favor of #3993.

@github-project-automation github-project-automation bot moved this from 🆕 New to 🏁 Done in 🧭 Planning Mar 25, 2024
@github-actions github-actions bot added the locked [bot] locked due to inactivity label Sep 22, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
duplicate indicate issues/PRs that are duplicates of another locked [bot] locked due to inactivity stale::recovered [bot] recovered after being marked as stale
Projects
Archived in project
Development

No branches or pull requests

3 participants