-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UTF-8 error with Python 3.6 (related with issue #27) #48
Comments
Did you tried export an env for Python 3 by running Or try
|
I tried both methods.
Output is:
|
Can you try: ...
ts = p.getTimeSeries("USDAM3L1Y=")
for record in ts:
print(record) |
Another idea is to set locale on your Ubuntu terminal like:
See if this helps. |
It doesn't help. (((
|
Any more ideas? |
Can you turn debug on and send the log file to our support@devcartel.com to take a look? We couldn't replicate the UnicodeDecodeError? Also not sure if this is only specific to timeseries. Can you try with normal subscription? |
I've sent the log.
No exceptions, data is received correctly. |
Hi, @wiwat-tharateeraparb . |
I sent below email but got no response. Here is some questions I need for finding the cause:
|
Hi Wiwat,
Value already set.
No. Any RICs raised error.
No effect. I try with
No effect.
With python 2.7.16 all work fine. PS. After second call getTimeSeries thrown error "RuntimeError: unidentifiable C++ exception":
|
We still couldn't reproduce this issue. We saw Python3 encoding error on Linux in the past and it's due to Is it possible we can access this time-series TS1 data? Let us know at support@devcartel.com. |
Same issue on windows as well, getting same error when trying to use with Python 3.6, someone in my team tried with python2.7 which is using ascii encoding and it worked fine. I would expect pyrfa to handle encoding correctly rather than clients dealing with it . |
timeseries = p.getTimeSeries("AAPL.OQ") |
To be totally honest, as we don't have enough sponsors to fund our PyRFA development. So we are not in the position to afford Refinitiv feeds to fix this issue. Since we are not able to fix for users, we open-sourced PyRFA so anyone who has access to the such data can fix it. |
Totally understandable, could you please do one favor? |
Config:
Example:
I've tried Python3.5 and Python 3.6. Pyrfa version is 8.5.2.
Usage:
PYTHONIOENCODING=utf-8 python3.6 timeseries.py
Error:
Originally posted by @snb2013 in #27 (comment)
The text was updated successfully, but these errors were encountered: