-
Notifications
You must be signed in to change notification settings - Fork 198
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
pyCue, pyOutline - Win10 python 2.7 requirements #175
Comments
When I deployed rqd to windows it was a small number of machines for use by Flix, but it was using Ice for RPC back then. It looks like the porting to protobuf may need some changes for windows support. Also its possible that pyoutline was not used on windows at the time. |
Thank you for the quick response ! Sorry my explanation of the issue may have been unclear. |
I don't think anyone has it running on windows yet and it will require some porting which may just be the issues found in #61 |
FYI pycue and pyoutline now support Python3 so this shouldn't be an issue anymore. |
Hi Team ,
Firstly thank you for Opensourcing this !!
I noticed you had a ticket for testing RDQ in windows...
I thought i might update this with some discoveries while trying build for win10 python2.7
in windows the python requirement of PySide2==5.11.2 does not appear to exist
So with that in mind PySide2==5.12 was used for the below results.
However I still find after a successful build of both pyCue and PyOutline I run into import issues
(venv) E:\gitHub\OpenCue\pyoutline>python
ActivePython 2.7.14.2717 (ActiveState Software Inc.) based on
Python 2.7.14 (default, Dec 15 2017, 16:31:45) [MSC v.1500 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
The broader question : should I attempt a windows build ?
The text was updated successfully, but these errors were encountered: