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

task for vendoring pluggy #2474

Closed
nicoddemus opened this issue Jun 6, 2017 · 2 comments · Fixed by #2523
Closed

task for vendoring pluggy #2474

nicoddemus opened this issue Jun 6, 2017 · 2 comments · Fixed by #2523
Assignees
Labels
type: infrastructure improvement to development/releases/CI structure

Comments

@nicoddemus
Copy link
Member

Next time we vendor pluggy, we should create an invoke task to do that automatically; also, the same task should update all internal links in the docs to point to the new location, for example:

same arguments as ``before`` but also a :py:class:`_CallOutcome`` object

To:

same arguments as ``before`` but also a :py:class:`_CallOutcome <_pytest.vendored_packages.pluggy._CallOutcome>` object
@nicoddemus nicoddemus added the type: infrastructure improvement to development/releases/CI structure label Jun 6, 2017
@The-Compiler
Copy link
Member

FWIW pip has https://github.com/pypa/pip/blob/master/tasks/vendoring/__init__.py - though they also do import rewriting and patching there.

@nicoddemus
Copy link
Member Author

xref: #2473

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: infrastructure improvement to development/releases/CI structure
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants