Tim Golden wrote:
Python.NET seems to sit in an awkward place in the ecosystem. Its niche seems to be: where you want a small bit of .NET technology (such as SQL-SMO in my case) but don't want to migrate any win-specific Python code. (ie stuff relying on pywin32)
Or, as in my case, you are developing a library and want to make use of some .NET technology, but don't want to force all the users of your library to use a non-standard Python implementation. -- Greg _______________________________________________ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
