From anton at wilddsl.net.au  Mon Dec  8 17:24:26 2008
From: anton at wilddsl.net.au (Anton Rolls)
Date: Tue, 09 Dec 2008 03:24:26 +1100
Subject: [melbourne-pug] Help understanding import metadata error
Message-ID: <493D4A3A.1090309@wilddsl.net.au>

Hello,

I'm trying to install PyOpenGL 3.0.0b8
from source (extracted to tmp directory), using Python 2.5.1:

	sudo python setup.py install

but it fails to import module 'metadata':

	Traceback (most recent call last):
	File "setup.py", line 7, in <module>
	import metadata
	ImportError: No module named metadata

I need help understanding this error.
Can anybody help?

I spent maybe an hour and a half searching web for
'metadata' ... (good luck to me).

I've installed Setuptools 0.6c9, if that helps.

Thanks for your consideration.

Regards,

Anton.

From ryan at rfk.id.au  Mon Dec  8 21:58:00 2008
From: ryan at rfk.id.au (Ryan Kelly)
Date: Tue, 09 Dec 2008 07:58:00 +1100
Subject: [melbourne-pug] Help understanding import metadata error
In-Reply-To: <493D4A3A.1090309@wilddsl.net.au>
References: <493D4A3A.1090309@wilddsl.net.au>
Message-ID: <1228769880.6314.4.camel@rambutan>


Hi Anton,

> 	Traceback (most recent call last):
> 	File "setup.py", line 7, in <module>
> 	import metadata
> 	ImportError: No module named metadata
> 
> I need help understanding this error.

Judging from the lines at the top of setup.py, it's expecting to find
the package "metadata" in the top-level source directory - but obviously
it isn't there.

A quick grep through the source reveals that setup.py is the only file
trying to use this module:


rfk at rambutan:~/PyOpenGL-3.0.0b8$ grep -r metadata *
OpenGL/error.py:		"""Initialise the GLError, storing metadata for later
display"""
setup.py:import metadata
setup.py:		**metadata.metadata



So perhaps you can just comment out the two uses of "metadata" in
setup.py?  I just tried this and it seems to install OK, but I don't
have any tests to run to see if it broke anything.


  Cheers,

     Ryan


-- 
Ryan Kelly
http://www.rfk.id.au  |  This message is digitally signed. Please visit
ryan at rfk.id.au        |  http://www.rfk.id.au/ramblings/gpg/ for details

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://mail.python.org/pipermail/melbourne-pug/attachments/20081209/aed373e1/attachment.pgp>

From ryan at rfk.id.au  Mon Dec  8 22:15:28 2008
From: ryan at rfk.id.au (Ryan Kelly)
Date: Tue, 09 Dec 2008 08:15:28 +1100
Subject: [melbourne-pug] Help understanding import metadata error
In-Reply-To: <1228769880.6314.4.camel@rambutan>
References: <493D4A3A.1090309@wilddsl.net.au>
	<1228769880.6314.4.camel@rambutan>
Message-ID: <1228770928.6314.17.camel@rambutan>


> So perhaps you can just comment out the two uses of "metadata" in
> setup.py?  I just tried this and it seems to install OK, but I don't
> have any tests to run to see if it broke anything.

Lies, there's a "tests" directory sitting right there in the source
folder - and they all pass despite commenting out the "metadata"
imports.


   Ryan

-- 
Ryan Kelly
http://www.rfk.id.au  |  This message is digitally signed. Please visit
ryan at rfk.id.au        |  http://www.rfk.id.au/ramblings/gpg/ for details

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://mail.python.org/pipermail/melbourne-pug/attachments/20081209/3f5cb3f2/attachment.pgp>

From stevecody at gmail.com  Tue Dec  9 23:55:11 2008
From: stevecody at gmail.com (Steve Cody)
Date: Wed, 10 Dec 2008 09:55:11 +1100
Subject: [melbourne-pug] Python, serial ports and OS
Message-ID: <93beb5450812091455h3ca6976eqfad3405dd7982238@mail.gmail.com>

Folks,

I have written a small utility to monitor a serial port for incoming data
from a wireless mesh network and decode it.

It works well on a Linux OS using the pySerial library.

On a Microsoft platform (WinXP) I get all sorts of access permission
problems with opening and using the serial port. I have tried on both a
genuine serial port and a USB<-> serial adaptor with the same result.

The Windows machine is on a corporate domain and I am running as a typical
user and not as Administrator. I have tried it on a second, different domain
with the same result so I am not sure if it is a user profile thing.

Any suggestions, diagnostic tests, tips, alternate serial port libraries,
etc. that might help me out of my bind?

Disclaimer: I chose python because of its cross-platform capability and I am
not trying to start any kind of OS holy war.

Steve
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/melbourne-pug/attachments/20081210/3bf07773/attachment.htm>

From skippy.hammond at gmail.com  Wed Dec 10 00:01:08 2008
From: skippy.hammond at gmail.com (Mark Hammond)
Date: Wed, 10 Dec 2008 10:01:08 +1100
Subject: [melbourne-pug] Python, serial ports and OS
In-Reply-To: <93beb5450812091455h3ca6976eqfad3405dd7982238@mail.gmail.com>
References: <93beb5450812091455h3ca6976eqfad3405dd7982238@mail.gmail.com>
Message-ID: <493EF8B4.7080209@gmail.com>

Steve Cody wrote:
> Folks,
> 
> I have written a small utility to monitor a serial port for incoming 
> data from a wireless mesh network and decode it.
> 
> It works well on a Linux OS using the pySerial library.
> 
> On a Microsoft platform (WinXP) I get all sorts of access permission 
> problems with opening and using the serial port. I have tried on both a 
> genuine serial port and a USB<-> serial adaptor with the same result.
> 
> The Windows machine is on a corporate domain and I am running as a 
> typical user and not as Administrator. I have tried it on a second, 
> different domain with the same result so I am not sure if it is a user 
> profile thing.
> 
> Any suggestions, diagnostic tests, tips, alternate serial port 
> libraries, etc. that might help me out of my bind?

I'd recommend trying the python-win32 at python.org mailing list - see 
http://mail.python.org/mailman/listinfo/python-win32 - but you probably 
should include more information, such as exactly how you are trying to 
access the serial port and the exact error message you see - I'm not 
aware of any special permissions needed, even on Windows Vista, to open 
a serial port.

Cheers,

Mark