-
Notifications
You must be signed in to change notification settings - Fork 155
Support Python 3.x #59
Comments
Remaining steps (in order of severity):
[0] Some test errors / failures that needs resolving:
|
As far as Thrift upgrade, we currently require unbound The main reason for this is that many services at Uber pin Thrift to older versions, and pip-compile won't be able to resolve it if we require Re |
I've got a collection of patches that I used to make Edit by @yurishkuro - I moved the diffs to https://pastebin.com/zuLge71t |
@dsludwig interesting - so you did not have to upgrade thrift-generated classes, just fix them up a bit? Or did you still have to use higher version of thrift? |
I still needed a higher version of thrift at runtime, but I did not end up regenerating the thrift classes. |
That's good to know. I started applying your patch to |
@dsludwig would you be able to test this? uber-common/opentracing-python-instrumentation#28 I didn't port all of your changes, e.g. this one
|
Does anyone know if there will be a new release in the near future? |
@olevold 3.6.1 was released on Sep 26, there have been no changes since then. |
The |
I made #99 to hopefully move this along |
What help is wanted for this issue? My environment is I was just able to get my django python3 app running with the latest pip installs after fixing one iteritems error: |
@kbroughton there have been a few PRs merged that fix various incompatibilities with py3, but it's not finished. Some PRs are not merged because they fail the tests (e.g. #101). The preference is to make a set of smaller PRs that fix specific syntax issues one at a time. |
@kbroughton I am surprised #113 addresses this issue. I just tried enabling 3.6 in #114, and it fails with a bunch of errors, like not recognizing |
Same question, what's left to be done here? Which help is needed? |
There are still some tests failing, most of them around unicode handling. We had an outage internally caused by unicode in python, it's currently being investigated, I am hoping it will finally reveal what was causing httplib to blow up, then we can have a proper fix and it should be easy to port to py3. |
I also see that we have some logic that skips installing
It looks like
Even if you fix that one, it gets harder from there.
|
@sc68cal yeah. I don't think there's much chance tchannel would be ever support py3, it's in maintenance mode. We have two options for Py3:
|
Should be fixed by #154 |
Congrats ! @yurishkuro do you know when a new release with Python 3 support will be done ? |
Planning to release it sometime this week. |
@yurishkuro - there's been a release but it does not say whether this has been merged into it or not. Could you clarify? I'm standing by to release flask tooling with py3 support. |
I was mentioned in the changelog, I just replicated as Github release https://github.com/jaegertracing/jaeger-client-python/releases/tag/v3.9.0 |
Related: #41, #43, #57
The text was updated successfully, but these errors were encountered: