Sean Cronin created AIRFLOW-954:
-----------------------------------
Summary: Installing future 0.16 breaks airflow initdb on Python 2.7
Key: AIRFLOW-954
URL: https://issues.apache.org/jira/browse/AIRFLOW-954
Project: Apache Airflow
Issue Type: Bug
Environment: Python 2.7.3 on Ubuntu 12.04 with a clean virtualenv and
HEAD of airflow master installed
Reporter: Sean Cronin
On master, if you run {{airflow initdb}} after installing HEAD of airflow
master with Python 2.7, you get the following error:
{code}
Traceback (most recent call last):
File "/home/sean/.virtualenvs/airflow-test/bin/airflow", line 17, in <module>
from airflow import configuration
File
"/home/sean/.virtualenvs/airflow-test/local/lib/python2.7/site-packages/airflow/__init__.py",
line 29, in <module>
from airflow import configuration as conf
File
"/home/sean/.virtualenvs/airflow-test/local/lib/python2.7/site-packages/airflow/configuration.py",
line 33, in <module>
from configparser import ConfigParser
ImportError: No module named configparser
{code}
This seems to be due to https://github.com/apache/incubator-airflow/pull/2091
which bumps {{future}} in {{setup.py}} so that future 0.16 can be installed.
Python future [got rid
of](http://python-future.org/whatsnew.html#what-s-new-in-version-0-16-0-2016-10-27)
their {{configparser}} alias in 0.16
The recommended way to fix this is to install {{future==0.16}} and install
{{configparser}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)