beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-2068) Upgrade Google-Apitools to latest version
Date Tue, 25 Apr 2017 22:15:04 GMT


ASF GitHub Bot commented on BEAM-2068:

GitHub user sb2nov opened a pull request:

    [BEAM-2068] Update to latest version of apitools

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [ ] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [ ] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [ ] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](
    R: @aaltay PTAL

You can merge this pull request into a Git repository by running:

    $ git pull BEAM-2068-upgrade-apitols

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2684
commit c0fa7473ccdb979ad2b52031d6af1406ddd4f567
Author: Sourabh Bajaj <>
Date:   2017-04-25T21:29:44Z

    [BEAM-2068] Update to latest version of apitools


> Upgrade Google-Apitools to latest version
> -----------------------------------------
>                 Key: BEAM-2068
>                 URL:
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-py
>            Reporter: Sourabh Bajaj
>            Assignee: Ahmet Altay
>            Priority: Minor
> In 0.5.9 apitools is pinned to setuptools 18.5 which is really old as the current release
is 35.0.1 at the time of creating the issue. Updating to 0.5.9 causes issues for other dependencies
so we're going to try to address this upstream first and then upgrade to the latest version
in the future.

This message was sent by Atlassian JIRA

View raw message