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

New branch, removes empty flag in SVN install command. Fixes SVN inst… #5993

Closed
wants to merge 2 commits into from

Conversation

rsilver23
Copy link

…alls

Thank you for contributing to Pipenv!

The issue

This branch fixes pipenv install of SVN repos. Pipenv was adding and extra empty argument when the verbosity flag was <= 0. This empty string was causing an error with SVN checkout commands.

The fix

This pull request removes the empty flag from the command arguments when the verbosity is not set.

@matteius
Copy link
Member

@rjsilver If you can check the ruff lint and add a news fragment, I may be able to include this in tonight's release.

@matteius
Copy link
Member

Actually I am pushing a fix to the ruff lint to main -- has nothing to do with this PR, but a news fragment would be good.

@rsilver23
Copy link
Author

rsilver23 commented Oct 24, 2023 via email

@matteius
Copy link
Member

@rsilver23 Basically create a file in the news directory 5993.bugfix.rst and explain the correction. Helpful to first run pre-commit install so that the linter will check your news file when you check it in.

@matteius
Copy link
Member

@rjsilver oh hey -- there is a problem I just noticed, which is you are modifying the pip internals. We don't want to do that, if there was truly a reason to do so, we would provide a patch, but I think in this case you mentioned it is something to do with click?

@matteius
Copy link
Member

@rjsilver I wonder if pypa/pip#11050 is related?

@rsilver23
Copy link
Author

@matteius pypa/pip#11050 definitely looks related

@rsilver23
Copy link
Author

@matteius looks like this code already exists in a patch. Do you have a better recommendation where to put this?

@matteius
Copy link
Member

@rsilver23 So we vendor in pip to pipenv and we have some patches that we apply after the fact. This feels like a case where pip itself would accept this patch, and the original PR that fixes it was tagged with needs a rebase. Perhaps you could open a new PR against pip -- the problem is, if I merge this as-is, the next time we vendor in a new version of pip it would get overwritten.

@@ -288,17 +288,22 @@ def fetch_new(
display_path(dest),
)
if verbosity <= 0:
flag = "--quiet"
cmd_args = make_command(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This definitely looks like something that would not encounter much resistance in upstream.

@devsagul
Copy link

Hi! FYI the original PR opened into pip repo and mentioned here has been merged.

@oz123
Copy link
Contributor

oz123 commented Apr 19, 2024

You mean this one? pypa/pip#11051?
As soon as there is new pip release, this will lend in pipenv too!

@matteius
Copy link
Member

That is great to hear -- we already regular vendor in pip, so I will close this PR as the plan is to go with the update in pip.

@matteius matteius closed this Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants