You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/03/09 05:08:38 UTC
[jira] [Commented] (AIRFLOW-954) Installing future 0.16 breaks
airflow initdb on Python 2.7
[ https://issues.apache.org/jira/browse/AIRFLOW-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15902503#comment-15902503 ]
ASF subversion and git services commented on AIRFLOW-954:
---------------------------------------------------------
Commit f3924696ff32942abc8c5709876c5717e0a82445 in incubator-airflow's branch refs/heads/master from [~seancron]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=f392469 ]
[AIRFLOW-954] Fix configparser ImportError
Fixes support for Python 2.7 since
https://github.com/apache/incubator-airflow/pull/2091 was merged
> 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)