Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/691
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/691#issuecomment-107391906
I'm going to merge this ...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/691#issuecomment-105501818
+1 to merge this
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/691#issuecomment-104338801
Okay, python should definitely work in the release, so let's go for the
short term fix first.
---
If your project is set up for it, you can reply to this email and
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/691#issuecomment-103471022
I think this is a hacky fix.
Sounds like the right approach is to have a python cli frontend that does
not expect a jar file.
---
If your project is set up
GitHub user rmetzger opened a pull request:
https://github.com/apache/flink/pull/691
[FLINK-2037] Provide flink-python.jar in lib/
I've tested the change locally with python3.
Please note that the code of `flink-language-binding-generic` is still in
`flink-dist.jar`. Only
