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 GitHub Bot (JIRA)" <ji...@apache.org> on 2019/07/05 07:50:00 UTC
[jira] [Commented] (AIRFLOW-4900) Incompatible version of Werkzeug
after Flask upgrade
[ https://issues.apache.org/jira/browse/AIRFLOW-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16879049#comment-16879049 ]
ASF GitHub Bot commented on AIRFLOW-4900:
-----------------------------------------
umanium commented on pull request #5535: [AIRFLOW-4900] Resolve incompatible version of Werkzeug
URL: https://github.com/apache/airflow/pull/5535
Make sure you have checked _all_ steps below.
### Jira
- [x] My PR addresses the following [Airflow Jira](https://issues.apache.org/jira/browse/AIRFLOW/) issues and references them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
- https://issues.apache.org/jira/browse/AIRFLOW-XXX
- In case you are fixing a typo in the documentation you can prepend your commit with \[AIRFLOW-XXX\], code changes always need a Jira issue.
- In case you are proposing a fundamental code change, you need to create an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)).
- In case you are adding a dependency, check if the license complies with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x).
### Description
- [x] Here are some details about my PR, including screenshots of any UI changes:
This PR Pin Werkzeug version to >= 0.15 as flask requirement needs it.
### Tests
- [x] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason:
No test added, because this is only changing requirements.
### Commits
- [x] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
1. Subject is separated from body by a blank line
1. Subject is limited to 50 characters (not including Jira issue reference)
1. Subject does not end with a period
1. Subject uses the imperative mood ("add", not "adding")
1. Body wraps at 72 characters
1. Body explains "what" and "why", not "how"
### Documentation
- [x] In case of new functionality, my PR adds documentation that describes how to use it.
- All the public functions and the classes in the PR contain docstrings that explain what it does
- If you implement backwards incompatible changes, please leave a note in the [Updating.md](https://github.com/apache/airflow/blob/master/UPDATING.md) so we can assign it to a appropriate release
### Code Quality
- [x] Passes `flake8`
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
> Incompatible version of Werkzeug after Flask upgrade
> ----------------------------------------------------
>
> Key: AIRFLOW-4900
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4900
> Project: Apache Airflow
> Issue Type: Bug
> Components: webserver
> Affects Versions: 1.10.3
> Reporter: Luqman Abdul Mushawwir
> Priority: Major
>
> On July 5th morning UTC+7, Flask have released version 1.1.0, which will be used in airflow because we have requirements for flask as follows: 'flask>=1.0, <2.0'
> However, flask pinned their Werkzeug to "Werkzeug>=0.15" which is incompatible with airflow's Werkzeug ('werkzeug>=0.14.1, <0.15.0'), resulting to error when doing "from airflow import model":
> _ERROR: Failure: ImportError (No module named 'werkzeug.wrappers.json'; 'werkzeug.wrappers' is not a package)_
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)