You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Ash Berlin-Taylor (JIRA)" <ji...@apache.org> on 2019/04/11 19:16:00 UTC
[jira] [Closed] (AIRFLOW-4290) Relax some package dependency ranges
[ https://issues.apache.org/jira/browse/AIRFLOW-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ash Berlin-Taylor closed AIRFLOW-4290.
--------------------------------------
Resolution: Later
Versions of dependencies is a known problem (see https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-9+Automated+Dependency+Management) , but those specific ones you you mentioned appear fine. Jinja2 is at 2.10.1 right now, and both future and configparser will go away when we drop support for Python2.
> Relax some package dependency ranges
> ------------------------------------
>
> Key: AIRFLOW-4290
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4290
> Project: Apache Airflow
> Issue Type: Task
> Components: dependencies
> Reporter: Zhitao Li
> Priority: Major
>
> Several package dependencies for Airflow are defined as a narrow version (future, jinja2, etc). The upper range for them is often old and below what people get from other packages' dependencies.
> I wonder whether we can relax their upper range so it spans more than one minor version, unless it's already known to be incompatible with Airflow.
> Several ones I can find through visual inspection:
> |'configparser>=3.5.0, <3.6.0',
> 'jinja2>=2.10.1, <2.11.0',
> 'future>=0.16.0, <0.17',|
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)