Re: [IronPython] Parsing scripts

2008-12-03 Thread orip
PySmell by Orestis Markou does completion through static analysis of Python code. I haven't tried it with IronPython but it could work, and from what I gather Orestis is happy to help. http://code.google.com/p/pysmell/ On Dec 4, 2:49 am, Dino Viehland <[EMAIL PROTECTED]> wrote: > The closest we ha

Re: [IronPython] Does IronPython 2.0 not recognize packages?

2008-12-02 Thread orip
If you have the following structure: Program.py PI /__init__.py /Authentication.py an empty __init__.py will allow you to do: import PI.Authentication from PI import Authentication If your __init__.py contains: import Authentication Then you can do: from PI import * and imp

Re: [IronPython] getframe and __file__

2008-11-16 Thread orip
That certainly fits my use case. It would be cool to check for an "IronPython Extensions" module and use it if available. On Nov 16, 7:39 pm, Michael Foord <[EMAIL PROTECTED]> wrote: > Hello guys, > > Around 90% of the uses for sys._getframe that I've seen are to find out > the calling module, by

Re: [IronPython] profiling ironpython application

2008-11-13 Thread orip
I'm interested in this as well - the last time a colleague tried this I think the .NET profiler didn't help. On Nov 13, 6:08 pm, Severin <[EMAIL PROTECTED]> wrote: > Hello, > > how do I profile a ironpython application? profile in a similar way as > 'cProfile' with CPython. > > my idea was to comp

Re: [IronPython] Cross-python development: detecting IronPython

2008-11-08 Thread orip
Thanks! On Nov 8, 10:47 pm, "Curt Hagenlocher" <[EMAIL PROTECTED]> wrote: > >>> import sys > >>> sys.platform > 'cli' > > On Sat, Nov 8, 2008 at 12:44 PM, orip <[EMAIL PROTECTED]> wrote: > > I'm sorry if this is a repea

[IronPython] Cross-python development: detecting IronPython

2008-11-08 Thread orip
I'm sorry if this is a repeat (my search abilities failed me), but what's the standard way to detect whether the current Python platform is IronPython? I usually prefer to check for abilities instead of platforms, but sometimes it's inevitable

Re: [IronPython] Porting from CPython: Figuring out the calling code's directory

2008-11-08 Thread orip
Great idea Michael, thanks! A small price to pay to make it work with IronPython. I'll probably make it optional (affect only IronPython users). On Nov 7, 1:21 pm, Michael Foord <[EMAIL PROTECTED]> wrote: > Why not change the API to: > >    return testoob.collecting.collect_from_files("test_*.py",

Re: [IronPython] Porting from CPython: Figuring out the calling code's directory

2008-11-08 Thread orip
- the use case is for building test suites: you can have a > subpackage of tests and define __init__.py like this: > > def suite(): >    import testoob >    return testoob.collecting.collect_from_files("test_*.py") > > Thanks, > orip. > > -- > Check out m