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.

Sign up for GitHub

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

Jump to bottom

Set InstallRequirement.metadata_directory, once metadata is generated #7088

Closed
pradyunsg opened this issue Sep 26, 2019 · 0 comments · Fixed by #7087
Closed

Set InstallRequirement.metadata_directory, once metadata is generated #7088

pradyunsg opened this issue Sep 26, 2019 · 0 comments · Fixed by #7087
Labels
auto-locked Outdated issues that have been locked by automation type: refactor Refactoring code

Comments

@pradyunsg
Copy link
Member

Eagerly assign to metadata_directory for legacy builds, once metadata is generated. (see get_dist(), egg_info_path, move_to_correct_build_directory())
@triage-new-issues triage-new-issues bot added the S: needs triage Issues/PRs that need to be triaged label Sep 26, 2019
@pradyunsg pradyunsg mentioned this issue Sep 26, 2019
Merged
@pradyunsg pradyunsg added the type: refactor Refactoring code label Sep 26, 2019
@triage-new-issues triage-new-issues bot removed the S: needs triage Issues/PRs that need to be triaged label Sep 26, 2019
@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Oct 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
auto-locked Outdated issues that have been locked by automation type: refactor Refactoring code
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Refactor metadata directory handling pradyunsg/pip
1 participant
@pradyunsg