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

ASF GitHub Bot commented on BEAM-2250:
--------------------------------------

GitHub user sb2nov opened a pull request:

    https://github.com/apache/beam/pull/3057

    [BEAM-2250] remove experimental and internal things from pydoc

    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`.
     - [ ] 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](https://www.apache.org/licenses/icla.pdf).
    
    ---
    
    R: @robertwb @aaltay PTAL

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

    $ git pull https://github.com/sb2nov/beam BEAM-2250-remove-pydoc

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

    https://github.com/apache/beam/pull/3057.patch

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

    This closes #3057
    
----
commit 928eb3e6a4c58b4ce549f09748a4ad1315b0b6b7
Author: Sourabh Bajaj <[email protected]>
Date:   2017-05-10T19:04:20Z

    [BEAM-2250] remove experimental and internal things from pydoc

----


> Remove FnHarness code from PyDocs
> ---------------------------------
>
>                 Key: BEAM-2250
>                 URL: https://issues.apache.org/jira/browse/BEAM-2250
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-py
>            Reporter: Sourabh Bajaj
>            Assignee: Ahmet Altay
>             Fix For: 2.0.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to