Mailman 3 January 2004 - Python.NET

Using an existing Python installation
by Mike Casaday 26 Feb '04

26 Feb '04

Python for .NET is really cool! Here's something I found out while trying to get it to work with my existing Python 2.3 installation. The README says: > **Can I use it with my existing Python installation?** > > Yes, at least on win32 systems. Just copy the files > Python.Runtime.dll and CLR.dll from the PythonNet directory to the > root directory of your python installation. > This answer comes with one caveat in my experience. For some reason you have to 'import CLR' before trying to import anything else from the .NET runtime. This isn't the case if I use the Python executable included in PythonNet-1.0-beta1.tgz, only if I use my existing Python installation. So this fails: from CLR.System.Reflection import Assembly Assembly.LoadWithPartialName('SomeNamespace') import CLR.SomeNamespace as SomeNamespace But this works: import CLR from CLR.System.Reflection import Assembly Assembly.LoadWithPartialName('SomeNamespace') import CLR.SomeNamespace as SomeNamespace Is it possible I'm doing something wrong (more than likely)? Is this a bug? Is this expected behavior? ZODB requires you to 'import ZODB' before you do certain things, so I wouldn't be surprised... ______________ mike P.S. I'm now playing around with the TrueVision3D game engine using Python, something that I couldn't really do until now. I'm happy I saw a link to this project from Daily Python-URL.

3 2

RE: [Python.NET] Problem whith DirectX device creation under pythonnet
by Brian Lloyd 22 Jan '04

22 Jan '04

[Copying the list on this as well, as it is probably relevant to everyone sooner or later...] Looking at this, I see what the issue is but I'm not sure how to address it, other than by documentation. The problem is the distinction between value types and reference types and how that distinction affects you when writing in Python. To take a boiled-down version of your example: items = CLR.System.Array.CreateInstance(Point, 3) for i in range(3): items[i] = Point(0, 0) items[0].X = 1 # won't work!! While the spelling of 'items[0].X = 1' is the same in C# and Python, there is an important and subtle semantic difference. In C# (and other compiled-to-IL languages), the compiler knows that Point is a value type and can do the Right Thing here, changing the value in place. In Python however, "everything's a reference", and there is really no spelling or semantic to allow it to do the right thing dynamically. The specific reason that items[0] itself doesn't change is that when you say 'items[0]', that getitem operation creates a Python object that holds a reference to the object at items[0] via a GCHandle. That causes a ValueType (like Point) to be boxed, so the following setattr ('.X = 1') *changes the state of the boxed value, not the original unboxed value*. Because there are no value type semantics or syntax in Python, there's not much the runtime can do about this :( The workaround is to do what you did, which is to make all of your changes to the boxed copy and then set (or re-set) the item in the array. This is not unlike some of the cases you can find in C# where you have to know about boxing behavior to avoid similar kinds of 'lost update' problems (generally because an implicit boxing happened that was not taken into account in the code). This is the same thing, just the manifestation is a little different in Python. The rule in Python is essentially: "the result of any attribute or item access is a boxed value", and as your example shows that can be important in how you approach your code. I've added a TODO to put a section about this into the docs - I'm sure it will be a FAQ. Brian Lloyd brian(a)zope.com V.P. Engineering 540.361.1716 Zope Corporation http://www.zope.com > -----Original Message----- > From: Laurent Caumont [mailto:lcaumont@pamdev.com] > Sent: Thursday, January 15, 2004 8:40 AM > To: Brian Lloyd > Subject: Re: [Python.NET] Problem whith DirectX device creation under > pythonnet > > > I have found a solution: > > self.vertexBuffer = > VertexBuffer(CustomVertex.TransformedColored, 3, > self.device, 0, CustomVertex.TransformedColored.Format, Pool.Default) > stm = self.vertexBuffer.Lock(0, 0, 0) > verts = > System.Array.CreateInstance(CustomVertex.TransformedColored, > 3) > > verts[0] = CustomVertex.TransformedColored(150, 50, 0.5, 1.0, > System.Drawing.Color.Aqua.ToArgb()) > ## verts[0].X = 150.0 > ## verts[0].Y = 50 > ## verts[0].Z = 0.5 > ## verts[0].Rhw = 1.0 > ## verts[0].Color = System.Drawing.Color.Aqua.ToArgb() > verts[1] = CustomVertex.TransformedColored(250, 250, 0.5, 1.0, > System.Drawing.Color.Brown.ToArgb()) > ## verts[1].X = 250 > ## verts[1].Y = 250 > ## verts[1].Z = 0.5 > ## verts[1].Rhw = 1.0 > ## verts[1].Color = System.Drawing.Color.Brown.ToArgb() > verts[2] = CustomVertex.TransformedColored(50, 250, 0.5, 1.0, > System.Drawing.Color.LightPink.ToArgb()) > ## verts[2].X = 50 > ## verts[2].Y = 250 > ## verts[2].Z = 0.5 > ## verts[2].Rhw = 1.0 > ## verts[2].Color = System.Drawing.Color.LightPink.ToArgb() > > stm.Write(verts) > self.vertexBuffer.Unlock() > > > I don't know why but the comment lines do not work: the values are not > changed. ( print verts[0].X = 0.0 ??) > > ----- Original Message ----- > From: "Laurent Caumont" <lcaumont(a)pamdev.com> > To: "Laurent Caumont" <lcaumont(a)pamdev.com> > Sent: Thursday, January 15, 2004 2:39 PM > Subject: Re: [Python.NET] Problem whith DirectX device creation under > pythonnet > > > > I have found a solution: > > > > self.vertexBuffer = > VertexBuffer(CustomVertex.TransformedColored, > 3, > > self.device, 0, CustomVertex.TransformedColored.Format, Pool.Default) > > stm = self.vertexBuffer.Lock(0, 0, 0) > > verts = > System.Array.CreateInstance(CustomVertex.TransformedColored, > > 3) > > > > verts[0] = CustomVertex.TransformedColored(150, 50, 0.5, 1.0, > > System.Drawing.Color.Aqua.ToArgb()) > > ## verts[0].X = 150.0 > > ## verts[0].Y = 50 > > ## verts[0].Z = 0.5 > > ## verts[0].Rhw = 1.0 > > ## verts[0].Color = System.Drawing.Color.Aqua.ToArgb() > > verts[1] = CustomVertex.TransformedColored(250, 250, 0.5, 1.0, > > System.Drawing.Color.Brown.ToArgb()) > > ## verts[1].X = 250 > > ## verts[1].Y = 250 > > ## verts[1].Z = 0.5 > > ## verts[1].Rhw = 1.0 > > ## verts[1].Color = System.Drawing.Color.Brown.ToArgb() > > verts[2] = CustomVertex.TransformedColored(50, 250, 0.5, 1.0, > > System.Drawing.Color.LightPink.ToArgb()) > > ## verts[2].X = 50 > > ## verts[2].Y = 250 > > ## verts[2].Z = 0.5 > > ## verts[2].Rhw = 1.0 > > ## verts[2].Color = System.Drawing.Color.LightPink.ToArgb() > > > > stm.Write(verts) > > self.vertexBuffer.Unlock() > > > > > > I don't know why but the comment lines do not work: the values are not > > changed. ( print verts[0].X = 0.0 ??) > > > > > > > > ----- Original Message ----- > > From: "Laurent Caumont" <lcaumont(a)pamdev.com> > > To: "Brian Lloyd" <brian(a)zope.com> > > Sent: Thursday, January 15, 2004 12:45 PM > > Subject: Re: [Python.NET] Problem whith DirectX device creation under > > pythonnet > > > > > > > YES. It works for me too ! > > > > > > I am very surprise that DirectX Documentation doesn't say > that it is an > > > array. > > > > > > About arrays, I have a question: > > > I try to convert this C# code to PythonNet like this: > > > > > > C#: > > > > > > vertexBuffer = new > VertexBuffer(typeof(CustomVertex.TransformedColored), > > 3, > > > dev, 0, CustomVertex.TransformedColored.Format, Pool.Default); > > > GraphicsStream stm = vertexBuffer.Lock(0, 0, 0); > > > CustomVertex.TransformedColored[] verts = new > > > CustomVertex.TransformedColored[3]; > > > verts[0].X=150;verts[0].Y=50;verts[0].Z=0.5f; verts[0].Rhw=1; > > verts[0].Color > > > = System.Drawing.Color.Aqua.ToArgb(); > > > verts[1].X=250;verts[1].Y=250;verts[1].Z=0.5f; verts[1].Rhw=1; > > > verts[1].Color = System.Drawing.Color.Brown.ToArgb(); > > > verts[2].X=50;verts[2].Y=250;verts[2].Z=0.5f; verts[2].Rhw=1; > > verts[2].Color > > > = System.Drawing.Color.LightPink.ToArgb(); > > > stm.Write(verts); > > > vertexBuffer.Unlock(); > > > > > > Python: > > > > > > self.vertexBuffer = VertexBuffer(CustomVertex.TransformedColored, 3, > > > self.device, 0, CustomVertex.TransformedColored.Format, Pool.Default) > > > stm = self.vertexBuffer.Lock(0, 0, 0) > > > verts = [] > > > verts.append(CustomVertex.TransformedColored(150, 50, 0.5, 1, > > > Color.Aqua.ToArgb())) > > > verts.append(CustomVertex.TransformedColored(250, 250, 0.5, 1, > > > Color.Brown.ToArgb())) > > > verts.append(CustomVertex.TransformedColored(50, 250, 0.5, 1, > > > Color.LightPink.ToArgb())) > > > > > > stm.Write(verts) > > > self.vertexBuffer.Unlock() > > > > > > > > > "stm.Write" doesn't like my verts array. (TypeError: no method matches > > given > > > arguments) > > > > > > I have remove the 'typeof' too but I don't know if it's ok ? > > > > > > Thanks for the Help. > > > > > > > > > ----- Original Message ----- > > > From: "Brian Lloyd" <brian(a)zope.com> > > > To: "Laurent Caumont" <lcaumont(a)pamdev.com> > > > Sent: Wednesday, January 14, 2004 10:01 PM > > > Subject: RE: [Python.NET] Problem whith DirectX device creation under > > > pythonnet > > > > > > > > > > I think I have an answer for you ;) Looking at the sig, the > > > > 'PresentParams' arg is actually PresentParams[] (iow, array > > > > of PresentParams rather than one). > > > > > > > > When I changed the call to: > > > > > > > > Device(0, DeviceType.Hardware, self, > > > CreateFlags.SofwareVertexProcessing, > > > > [presentParams]) > > > > > > > > it worked for me. > > > > > > > > > > > > Brian Lloyd brian(a)zope.com > > > > V.P. Engineering 540.361.1716 > > > > Zope Corporation http://www.zope.com > > > > > > > > > > > > > -----Original Message----- > > > > > From: Laurent Caumont [mailto:lcaumont@pamdev.com] > > > > > Sent: Wednesday, January 14, 2004 4:54 AM > > > > > To: Brian Lloyd > > > > > Subject: Re: [Python.NET] Problem whith DirectX device creation > under > > > > > pythonnet > > > > > > > > > > > > > > > Hi Brian, > > > > > > > > > > Yes, I use the b3 release. > > > > > > > > > > I suspect the enum to be the cause of the error. > > > > > > > > > > If you do that: > > > > > "dtype = DeviceType.Hardware" > > > > > dtype is a "int" not a "DeviceType" (enum). > > > > > > > > > > But the constructor need a "DeviceType" not a "int". > > > > > > > > > > Is it possible with pyton to force the type (cast)? > > > > > > > > > > Thanks. > > > > > > > > > > ----- Original Message ----- > > > > > From: "Brian Lloyd" <brian(a)zope.com> > > > > > To: "Laurent Caumont" <lcaumont(a)pamdev.com>; > <pythondotnet(a)python.org> > > > > > Sent: Tuesday, January 13, 2004 4:43 PM > > > > > Subject: RE: [Python.NET] Problem whith DirectX device creation > under > > > > > pythonnet > > > > > > > > > > > > > > > > > I use the "DirectX 9.0 SDK Update (Summer 2003)" > documentation. > > > > > > > > > > > > > > This C# sample is very close to my code. > > > > > > > It use the same constructor. > > > > > > > > > > > > > > Is there any way to view the constructor signature > with python ? > > > > > > > > > > > > > > Laurent. > > > > > > > > > > > > Not currently, though I've put it on the todo list (I > think I can > > > > > > have SomeClass.__doc__ display constructor info). > > > > > > > > > > > > Your code _looks_ right, which makes me suspect that the Python > > > > > > integration layer is somehow mishandling one of the arguments. I > > > > > > don't have managed directx handy, so I don't have a quick way > > > > > > to check that theory :( > > > > > > > > > > > > If you're inclined, you can probably hack the > MethodBinder.cs file > > > > > > to log what it's doing when it tries to convert the arguments. > I'll > > > > > > try to get mdx installed to try to reproduce it myself, > but it may > > > > > > be a few days. > > > > > > > > > > > > Just to be sure - you are using the latest beta, right? > Beta 2 had > > > > > > a bug that caused problems calling ctors, so make sure you are > > > > > > using the b3 release. > > > > > > > > > > > > > > > > > > Brian Lloyd brian(a)zope.com > > > > > > V.P. Engineering 540.361.1716 > > > > > > Zope Corporation http://www.zope.com > > > > > > > > > > > > > > > > > > > > > > > > > > > > >

2 5

followup: import works only after failed import
by Leonard :paniq: Ritter 15 Jan '04

15 Jan '04

update: it seems as if import CLR from CLR.QuenceNET import bla does the trick, however that doesnt work on the python prompt. anyway, so far it all works great in the code, thanks for that wrapper, brian, with your work you have already filled a big hole in the compatibility chain. ----------------8<-------------------------- this is even funnier. importing a .net assembly seems only to work if the dll has been loaded before. in each try, i restart python from the directory where the .net DLL is located. first try: O:\Quence\debug>python Python 2.3.2 (#49, Oct 2 2003, 20:02:00) [MSC v.1200 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> import CLR.QuenceNET Traceback (most recent call last): File "<stdin>", line 1, in ? ImportError: No module named QuenceNET second try: O:\Quence\debug>python Python 2.3.2 (#49, Oct 2 2003, 20:02:00) [MSC v.1200 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> import CLR >>> import CLR.QuenceNET Traceback (most recent call last): File "<stdin>", line 1, in ? ImportError: No module named QuenceNET >>> import QuenceNET Traceback (most recent call last): File "<stdin>", line 1, in ? ImportError: dynamic module does not define init function (initQuenceNET) >>> import CLR.QuenceNET >>> dir(CLR.QuenceNET) ['__doc__', '__name__'] third try (optimized): O:\Quence\debug>python Python 2.3.2 (#49, Oct 2 2003, 20:02:00) [MSC v.1200 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> import CLR >>> import QuenceNET Traceback (most recent call last): File "<stdin>", line 1, in ? ImportError: dynamic module does not define init function (initQuenceNET) >>> import CLR.QuenceNET >>> dir(CLR.QuenceNET) ['__doc__', '__name__'] fourth try (variant): O:\Quence\debug>python Python 2.3.2 (#49, Oct 2 2003, 20:02:00) [MSC v.1200 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> import QuenceNET Traceback (most recent call last): File "<stdin>", line 1, in ? ImportError: dynamic module does not define init function (initQuenceNET) >>> import CLR.QuenceNET Traceback (most recent call last): File "<stdin>", line 1, in ? ImportError: No module named QuenceNET >>> import QuenceNET Traceback (most recent call last): File "<stdin>", line 1, in ? ImportError: dynamic module does not define init function (initQuenceNET) >>> import CLR.QuenceNET >>> dir(CLR.QuenceNET) ['__doc__', '__name__'] so to import my custom assembly in python, the code currently looks like this: import CLR try: import QuenceNET # for the error except: pass # catch import CLR.QuenceNET -- Leonard Ritter -- paniq(a)gmx.net -- http://www.quence.com -- http://www.paniq.de

2 1

aspx
by Boyan Hristov 15 Jan '04

15 Jan '04

Is there any posibility to use PythonNet in asp.net application insted c# or vb like in asp. I embed PythonNet in a c# asp application but there are too many problems... -- Best Regards, Boyan

2 1

import works only after failed import
by Leonard :paniq: Ritter 14 Jan '04

14 Jan '04

this is even funnier. importing a .net assembly seems only to work if the dll has been loaded before. in each try, i restart python from the directory where the .net DLL is located. first try: O:\Quence\debug>python Python 2.3.2 (#49, Oct 2 2003, 20:02:00) [MSC v.1200 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> import CLR.QuenceNET Traceback (most recent call last): File "<stdin>", line 1, in ? ImportError: No module named QuenceNET second try: O:\Quence\debug>python Python 2.3.2 (#49, Oct 2 2003, 20:02:00) [MSC v.1200 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> import CLR >>> import CLR.QuenceNET Traceback (most recent call last): File "<stdin>", line 1, in ? ImportError: No module named QuenceNET >>> import QuenceNET Traceback (most recent call last): File "<stdin>", line 1, in ? ImportError: dynamic module does not define init function (initQuenceNET) >>> import CLR.QuenceNET >>> dir(CLR.QuenceNET) ['__doc__', '__name__'] third try (optimized): O:\Quence\debug>python Python 2.3.2 (#49, Oct 2 2003, 20:02:00) [MSC v.1200 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> import CLR >>> import QuenceNET Traceback (most recent call last): File "<stdin>", line 1, in ? ImportError: dynamic module does not define init function (initQuenceNET) >>> import CLR.QuenceNET >>> dir(CLR.QuenceNET) ['__doc__', '__name__'] fourth try (variant): O:\Quence\debug>python Python 2.3.2 (#49, Oct 2 2003, 20:02:00) [MSC v.1200 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> import QuenceNET Traceback (most recent call last): File "<stdin>", line 1, in ? ImportError: dynamic module does not define init function (initQuenceNET) >>> import CLR.QuenceNET Traceback (most recent call last): File "<stdin>", line 1, in ? ImportError: No module named QuenceNET >>> import QuenceNET Traceback (most recent call last): File "<stdin>", line 1, in ? ImportError: dynamic module does not define init function (initQuenceNET) >>> import CLR.QuenceNET >>> dir(CLR.QuenceNET) ['__doc__', '__name__'] so to import my custom assembly in python, the code currently looks like this: import CLR try: import QuenceNET # for the error except: pass # catch import CLR.QuenceNET -- Leonard Ritter -- paniq(a)gmx.net -- http://www.quence.com -- http://www.paniq.de

1 0

error: ImportError: dynamic module does not define init function (initASSEMBLYNAME)
by Leonard :paniq: Ritter 14 Jan '04

14 Jan '04

when loading a mixed managed c++ library that i use as .net wrapper for my object model, i get >>> import QuenceNET Traceback (most recent call last): File "<stdin>", line 1, in ? ImportError: dynamic module does not define init function (initQuenceNET) does anyone have specific background information on that error and how i can avoid it? there is no problem using the assembly in .net. i was trying to import the library after changing to the directory where the dll is located. -- Leonard Ritter -- paniq(a)gmx.net -- http://www.quence.com -- http://www.paniq.de

2 1

Problem whith DirectX device creation under pythonnet
by Laurent Caumont 13 Jan '04

13 Jan '04

I use the "DirectX 9.0 SDK Update (Summer 2003)" documentation. This C# sample is very close to my code. It use the same constructor. Is there any way to view the constructor signature with python ? Laurent. ----------------------------------------- Laurent CAUMONT 3D Engineer lcaumont(a)pamdev.com PAM Development 110 rue du Lt Petit Leroy 94550 CHEVILLY LARUE FRANCE Tél : +33.1.46.87.44.12 Fax : +33.1.46.87.45.57 Internet : www.pamdev.com ------------------------------------------

2 1

Problem whith DirectX device creation under pythonnet
by Laurent Caumont 12 Jan '04

12 Jan '04

Hello, I want to create a Directx 9.0 application with Python and Managed Directx. Here is the code: import CLR.System.Windows.Forms as WinForms from CLR.System.Drawing import Size, Point import CLR.Microsoft.DirectX import CLR.Microsoft.DirectX.Direct3D from CLR.Microsoft.DirectX import Matrix from CLR.Microsoft.DirectX.Direct3D import Device, PresentParameters, SwapEffect, DeviceType, CreateFlags class DirectXWindow(WinForms.Form): """A simple hello world app that demonstrates the essentials of winforms programming and event-based programming in Python.""" def CreateDevice(self): presentParams = PresentParameters() presentParams.Windowed = True presentParams.SwapEffect = SwapEffect.Discard device = Device(0, DeviceType.Hardware, self, CreateFlags.SoftwareVertexProcessing, presentParams) def __init__(self): self.Text = "DirectX Window" self.AutoScaleBaseSize = Size(100, 100) self.ClientSize = Size(400, 300); h = WinForms.SystemInformation.CaptionHeight self.MinimumSize = Size(392, (117 + h)) self.CreateDevice() def run(self): WinForms.Application.Run(self) def main(): DirectXWindow().run() if __name__ == '__main__': main() I have the error: > File "Directx.py", line 18, in CreateDevice > TypeError: no constructor matches given arguments Form the DirectX documentation, there are 3 constructors available: public Device (Int32, DeviceType, IntPtr, CreateFlags, PresentParameters) public Device (Int32, DeviceType, Control, CreateFlags, PresentParameters) public Device (IntPtr) The Int32 is the DeviceNum (0). DeviceType and CreateFlags are 2 enum. PresentParameters is a Structure. The 'help(Device)' does'nt work. How can I display all the signature of all constructors ? What is the problem ? Thanks for the help.

2 1

Python.Net affected by currently somewhat broken .Net Multithreading?
by Martin Kretschmar 10 Jan '04

10 Jan '04

Hello, the well respected german computer magazine c't reports in an article of its release 26/03 on page 214, that the .Net multithreading support currently suffers from several strangeness factors. The class ThreadPool suffers from several anomalies: The thread pool of a process is limited by 25 threads per processor. GetMaxThreads() and GetAvailableThreads() deliver the values 25/25 with .Net 1.0 and 25/1000 with .Net 1.1. The new threads obey to a pretty ackward activation pattern, new threads are started with individual offsets of 500ms to each other! The garbage collector starts after one minute after the demise of a thread. If new threads are requested in between, one again suffers the 500ms penalties from above. Further experiments trying to start all required threads in advance suffered from being queued automatically from thread 25 on, so this didn't help so much either. Running one thread under full load, makes the system take up to 5 seconds to start another thread. Attempts to work without ThreadPool suffered also from several anomalies and could even crash the .Net executive: The executive is quiet sensitive when one tries to Resume() an already running process etc, which might mean some extra private bookkeeping. Attempts with subclassing BaseThread worked but occasionally resulted in a termination with return code 0 with .Net 1.0 and a reported stack overflow with .Net 1.1. Closing a window while one owns homemade background thread is running creates a zombie thread. Altogether the authors hope, that further releases of .Net like .Net 2.0 will help to improve the situation. Regards, Martin

1 0

Initial Script Directory?
by Michael Reitzenstein 10 Jan '04

10 Jan '04

I have almost finished my first full project using .Net & Python, however when trying the program out on other computers I have hit a problem when importing modules. I couldn't figure out how to set the directory that Python should search to import modules when I first started integrating Python into my application, so I did a kludge-y method where I copied the script into the program's main directory, ran it, and then deleted the script and its compiled equivalent once it had been ran. This works fine on my machine - but I sent it to my friend to test out, and it wouldn't work. The scripts would copy over fine into the program's main directory, but an exception would be tripped when attempting to import the module. I am guessing that the directory that Python searches in is incorrect (not defined?) on their machine. I attempted the following at the very start of my program: string Dir = System.Windows.Forms.Application.ExecutablePath; System.Environment.CurrentDirectory = Dir.Replace( "Buildmeister.exe", "" ); ProgramDir = System.Environment.CurrentDirectory; Python.Runtime.PythonEngine.Initialize( ); Python.Runtime.PythonEngine.RunSimpleString( "sys.path[ 0 ] = '" + ProgramDir + "'" ); Python.Runtime.PythonEngine.RunSimpleString( "chdir( '" + ProgramDir + "'" ); ...But it doesn't work! Is there any simple way to set the directory that python searches for modules? --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.529 / Virus Database: 324 - Release Date: 16/10/2003

1 0