-
Notifications
You must be signed in to change notification settings - Fork 305
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
Initialization exception on windows 7 #47
Comments
Feedback from customer - it works if using python 2.7. We could add a note to the README? |
Thanks @samanthadrago. Do you know which version they were using ? |
@yannmh 3.4 |
Thanks @samanthadrago. |
@yannmh, I think I found a solution. I tested it out and it worked for me. According to a comment by eryksun in "http://stackoverflow.com/questions/626796/how-do-i-find-the-windows-common-application-data-folder-using-python" (provided in the code) ctypes.create_unicode_buffer should be used rather than wintypes.create_unicode_buffer. This is because "[create_unicode_buffer] was only accidentally in wintypes in PY2 due to its use of from ctypes import *" I was on Windows 7 using Python 3.4 in a virtual environment with PyCharms as my IDE. |
Because '[create_unicode_buffer] was only accidentally in wintypes in PY2 due to its use of from ctypes import *'. More info http://stackoverflow.com/questions/626796/how-do-i-find-the-windows-common-application-data-folder-using-python
Thanks a lot @apoorvab. |
fix #47 py34 windows initialization issue
Initializing datadogpy on windows7 results in the exception below.
Note: running python 3.4
The text was updated successfully, but these errors were encountered: