I think this issue more revolves around PyGLEW, but LaunchPad won't let me report to them...

I've taken a screenshot of the issue rather than trying to explain it:
http://lh3.ggpht.com/-d6gM0Qlq9Ek/UjhxFDFOmAI/AAAAAAAAFIU/Vwell0V1Vo8/s1400/error.jpg

I've also notified the PyGPU developers who require the installation for their project.

You are correct, this is not likely to be a problem with Python itself (the interactive prompt in your screen capture doesn't look like what Python would produce by itself).  So, since it is almost certainly not a bug in Python, it's not appropriate for this issue tracker.

(The fact that the import fails probably means that PyGLEW didn't compile or install correctly.)

yeh... the only thing I was thinking was on Python's end was the DLL
(Highlighted in the img) failing to register.
(I have seen cases of PYD modules used in the same manner, such as PyWin32
modules)

but yea, I see now that isn't the case, so thank you :)

On Tue, Sep 17, 2013 at 12:36 PM, R. David Murray <report@bugs.python.org>wrote:

>
> R. David Murray added the comment:
>
> You are correct, this is not likely to be a problem with Python itself
> (the interactive prompt in your screen capture doesn't look like what
> Python would produce by itself).  So, since it is almost certainly not a
> bug in Python, it's not appropriate for this issue tracker.
>
> (The fact that the import fails probably means that PyGLEW didn't compile
> or install correctly.)
>
> ----------
> nosy: +r.david.murray
> resolution:  -> invalid
> stage:  -> committed/rejected
> status: open -> closed
> type: compile error ->
> versions: +3rd party -Python 2.7
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue19041>
> _______________________________________
>