search

AnacondaRecipes / repodata-hotfixes

Changes to package metadata to fix behavior
BSD 3-Clause "New" or "Revised" License
14 stars 20 forks source link

Recent jinja2 are no longer a problem for conda-build #182

Closed dholth closed 1 year ago

dholth commented 1 year ago

With conda's tests depending on flask and jinja2 through conda-build, and jinja2 3.0.1 / 3.0.2 which may fix the issue being rather old by now, drop this problematic constraint.

https://metayaml-conda.fly.dev/metayaml/newest_by_platform?name=jinja2

Should we express a "this jinja2 version is not allowed" dependency?

dholth commented 1 year ago

I updated the PR to exclude 3.0.0 only (could have been 3.0.*). Defaults has 2.x and 3.1.x only. Not sure how to reproduce the conda-build problem if we wanted to be precise. conda-forge's hotfixes and recipe don't care about conda-build's jinja2 version.