Remove jinja2 checks since it is already an explicit dependency
#5497
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
conda-bot
added
the
cla-signed
CodSpeed Performance ReportMerging #5497 will not alter performanceComparing Summary
|
beeankha
previously approved these changes
Sep 20, 2024
beeankha
reviewed
Sep 22, 2024
jaimergp
approved these changes
Sep 25, 2024
beeankha
approved these changes
Sep 26, 2024
jezdez
approved these changes
Oct 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Found some try-except clauses around
jinja2imports. These are no longer necessary (or desired) sincejinja2is a hard dependency ofconda-buildand will always be present.Checklist - did you ...
newsdirectory (using the template) for the next release's release notes?Add / update outdated documentation?