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 freeze changed behaviour in 8.1.0 #3616

Closed
sbidoul opened this Issue Apr 14, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@sbidoul
Contributor

sbidoul commented Apr 14, 2016

  • Pip version: >=8.1.0
  • Python version: any
  • Operating System: any

Description:

0c22107 introduced a regression in the sense that pip freeze now returns a different remote than before even when origin is present. This breaks existing workflows.

What I've run:

Before: pip freeze returned the origin remote
After: pip freeze return the "first" remote

Is there a chance to have the new code trigger only when origin is not found?

cc/ @hashar

@xavfernandez

This comment has been minimized.

Show comment
Hide comment
@xavfernandez

xavfernandez Apr 26, 2016

Contributor

Is there a chance to have the new code trigger only when origin is not found?

Since origin is the default remote name, it could make sense. PR welcome ;)

Contributor

xavfernandez commented Apr 26, 2016

Is there a chance to have the new code trigger only when origin is not found?

Since origin is the default remote name, it could make sense. PR welcome ;)

@sbidoul

This comment has been minimized.

Show comment
Hide comment
@sbidoul

sbidoul May 21, 2016

Contributor

@xavfernandez here is the PR, with a test. #3708

Contributor

sbidoul commented May 21, 2016

@xavfernandez here is the PR, with a test. #3708

@dstufft dstufft closed this in #3708 May 21, 2016

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