Skip to content

Conda: protect against None when appending core requirements #8077

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

Merged
merged 1 commit into from
Apr 8, 2021

Conversation

@stsewd stsewd requested a review from a team April 8, 2021 02:07
@@ -615,7 +615,7 @@ def _append_core_requirements(self):

for item in dependencies:
if isinstance(item, dict) and 'pip' in item:
pip_requirements.extend(item.get('pip', []))
pip_requirements.extend(item.get('pip') or [])
Copy link
Member

Choose a reason for hiding this comment

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

Worth a comment here.

Copy link
Member

Choose a reason for hiding this comment

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

@stsewd the comment you added in the description of the PR is a good one. "pip can be None" says less than the description, where you explained the reason of pip being None which adds good context to the problem.

@stsewd stsewd force-pushed the protect-agains-none branch from 567493d to bfa0e7e Compare April 8, 2021 15:47
@stsewd stsewd enabled auto-merge (squash) April 8, 2021 15:47
@stsewd stsewd merged commit bc3e147 into master Apr 8, 2021
@stsewd stsewd deleted the protect-agains-none branch April 8, 2021 15:54
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.

3 participants