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/10/14 18:59:00 UTC

[jira] [Commented] (AIRFLOW-5657) Upgrade dill dependency

    [ https://issues.apache.org/jira/browse/AIRFLOW-5657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16951251#comment-16951251 ] 

ASF GitHub Bot commented on AIRFLOW-5657:
-----------------------------------------

aaltay commented on pull request #6334: [AIRFLOW-5657] Update the upper bound for dill
URL: https://github.com/apache/airflow/pull/6334
 
 
   There is a new 0.3.x version line for dill. This change increases the range to allow using new dill versions. This also makes airflow compatible with beam.
   
   ### Jira
   
   - [ ] 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
   
   - [ ] Here are some details about my PR, including screenshots of any UI changes:
   
   ### Tests
   
   - [ ] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason:
   
   ### Commits
   
   - [ ] 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
   
   - [ ] 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
   
 
----------------------------------------------------------------
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


> Upgrade dill dependency
> -----------------------
>
>                 Key: AIRFLOW-5657
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-5657
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: dependencies
>    Affects Versions: 1.10.6
>            Reporter: Ahmet Altay
>            Priority: Major
>
> Airflow depends on "dill>=0.2.2, <0.3'," (https://github.com/apache/airflow/blob/1a4c16432b8718189269e63c3afcd2709eed7379/setup.py#L359).
> However there is a new 0.3.x range for dill (https://pypi.org/project/dill/)
> I would like to upgrade the version to the same range that matches Apache Beam's version.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)