Re: [IronPython] Exposing C++/CLI template classes to ironpython

2007-01-04 Thread Dino Viehland
Unfortunately you can't the CPython extension libraries w/ IronPython. You could do it w/ templates instead of macros and force the instantiation of the generic public class like: template class NativeData { public: T foo; }; template public ref class GenericData { private: Nat

Re: [IronPython] Python Command Line Compiler issues and questions

2007-01-04 Thread Dino Viehland
I am surprised one is behaving different. It works for me w/ pyc if I keep the package directory on the path, but if I don't then it breaks. I'm curious did you include all of your individual package files, or just __init__.py? And were the packages on your path? -Original Message- Fr

Re: [IronPython] Python Command Line Compiler issues and questions

2007-01-04 Thread Michael Foord
Dino Viehland wrote: > I am surprised one is behaving different. It works for me w/ pyc if I keep > the package directory on the path, but if I don't then it breaks. > > I'm curious did you include all of your individual package files, or just > __init__.py? And were the packages on your path?

Re: [IronPython] Python Command Line Compiler issues and questions

2007-01-04 Thread Patrick O'Brien
On 1/4/07, Dino Viehland <[EMAIL PROTECTED]> wrote: I am surprised one is behaving different. It works for me w/ pyc if I keep the package directory on the path, but if I don't then it breaks. I'm curious did you include all of your individual package files, or just __init__.py? And were the

Re: [IronPython] Python Command Line Compiler issues and questions

2007-01-04 Thread Dino Viehland
That works for me, I did it a little differently, but basically the same: a: import b print 'hello' b.foo() b: print 'goodbye' def foo(): print 42 >ipy pyc.py /target:exe /main:a.py b.py ... >a.exe goodbye hello 42 That works even if a.py and b.py aren't available after the compilation. What

Re: [IronPython] Python Command Line Compiler issues and questions

2007-01-04 Thread Michael Foord
Dino Viehland wrote: > That works for me, I did it a little differently, but basically the same: > > a: > import b > print 'hello' > b.foo() > > b: > print 'goodbye' > def foo(): print 42 > >> ipy pyc.py /target:exe /main:a.py b.py > ... > >> a.exe > goodbye > hello > 42 > > That works even if

Re: [IronPython] Python Command Line Compiler issues and questions

2007-01-04 Thread Dino Viehland
I've opened CodePlex bug 7011 for this (http://www.codeplex.com/IronPython/WorkItem/View.aspx?WorkItemId=7011). Feel free to vote on it to raise its visibility! :). -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Foord Sent: Thursday, January 04

Re: [IronPython] Python Command Line Compiler issues and questions

2007-01-04 Thread Patrick O'Brien
On 1/4/07, Michael Foord <[EMAIL PROTECTED]> wrote: I thought it worked with makeexe.py, but renaming the package causes the executable to fail. Oh well. That's actually good to hear because makeexe is really just pyc with fewer options - the basic mechanism is identical. Should make it easi

Re: [IronPython] Python Command Line Compiler issues and questions

2007-01-04 Thread Patrick O'Brien
On 1/4/07, Dino Viehland <[EMAIL PROTECTED]> wrote: That works for me, I did it a little differently, but basically the same: I apologize. I just tried to reproduce the problem I was having and found a mistake in the batch file I had created to send the right options to PYC. So it is true t