[PyCUDA] Re: Import Error: No module named compyte.dtypes

2019-05-24 Thread Dan Guralnik
uda/releases/tag/v2019.1>. I keep forgetting that the Github source releases don't include the compyte code. Christoph On 5/24/2019 11:33 AM, Andreas Kloeckner wrote: Dan Guralnik writes: Thanks! Actually, I originally got the wheel from (https://www.lfd.uci.edu/~gohlke/pythonlibs/#

[PyCUDA] Import Error: No module named compyte.dtypes

2019-05-23 Thread Dan Guralnik
Hello, When attempting to run pycuda (the latest 2019 version), I encounter the following error message from python (2.7): -- File "test_cuda.py", line 9, in import pycuda.tools File "C:\Users\kotmasha\Anaconda2\lib\site-packages\pycuda\tools.py", line 44, in from

[PyCUDA] Re: Import Error: No module named compyte.dtypes

2019-05-24 Thread Dan Guralnik
g the same results. Could this have anything to do with my doing this on a Windows 10 machine? - Dan On 5/23/2019 11:42 PM, Andreas Kloeckner wrote: Dan Guralnik writes: Hello, When attempting to run pycuda (the latest 2019 version), I encounter the following error message from p

[PyCUDA] Re: gpuarray.zeros / to_gpu crash

2019-11-18 Thread Dan Guralnik
Thank you, Andreas. Your suggestion worked, but with a tweak: had to use one of the architecture-specific versions of vcvars (vcvars64.bat) in my case. Another alternative (for VS 2019) turned out to be running under one of the VS-provided developer command prompts: they load their own batch