Skip to content

Switch to a dedicated tool for Pipenv’s own vendoring process #4075

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

Closed
uranusjr opened this issue Dec 19, 2019 · 2 comments
Closed

Switch to a dedicated tool for Pipenv’s own vendoring process #4075

uranusjr opened this issue Dec 19, 2019 · 2 comments
Labels
Category: Development Issue affects development workflow. Type: Discussion This issue is open for discussion. Type: Maintenance 🚧 This issue pertains to maintenance of pipenv itself.

Comments

@uranusjr
Copy link
Member

pip recently moved their vendoring tasks to a separate project (pypa/pip#7485). We might want to reuse that since Pipenv’s vendoring tasks are largely modelled after pip.

cc @pradyunsg @techalchemy

@ghost ghost added the triage label Dec 19, 2019
@pradyunsg
Copy link
Member

Yeah, I'll file a PR for this soon-ish.

First though, I need to improve the messaging based on the latest comment by @dstufft to discourage use by folks who don't definitely need it (basically everyone except pip and similar tools), since we don't want to make life harder for redistributors who don't like vendored packages.

@uranusjr uranusjr added Category: Development Issue affects development workflow. Type: Discussion This issue is open for discussion. Type: Maintenance 🚧 This issue pertains to maintenance of pipenv itself. and removed triage labels Dec 19, 2019
@techalchemy
Copy link
Member

techalchemy commented Dec 20, 2019 via email

@matteius matteius closed this as not planned Won't fix, can't repro, duplicate, stale Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category: Development Issue affects development workflow. Type: Discussion This issue is open for discussion. Type: Maintenance 🚧 This issue pertains to maintenance of pipenv itself.
Projects
None yet
Development

No branches or pull requests

4 participants