[IronPython] pywin32 on Iron Python?

Jeff Hardy jdhardy at gmail.com
Wed Apr 29 20:37:24 CEST 2009

On Wed, Apr 29, 2009 at 10:55 AM, Dave Fugate <dfugate at microsoft.com> wrote:
> The technical bar for inclusion of 3rd party tests into our checkin system is pretty simple - the test process needs to emit a non-zero exit code when it fails.  When some portion of a test fails under IronPython for whatever reason, we simply disable that portion.  For example, we run around 200 CPython 2.6 test_*.py files for every IronPython checkin with roughly a thousand individual test cases in these modules disabled.  With this in mind, it likely doesn't matter that most of Django's test suite does not pass => we can disable the broken stuff.

In the case of Django, many of the tests depnd on a database. Is there
anyway for you guys to handle that, or would you only be able to run
the tests that don't need a db? You could use SQLite, but that
requires an sqlite module, and you're back into 3rd party code again.

> As for inclusion of commit messages in the CodePlex source synchs, we'll look into this.  It's a bit challenging as sometimes we work on getting IronPython running against/with the latest unannounced Microsoft technology (e.g., we had IronPython running under Silverlight months before Silverlight was publically announced) and this is often reflected in our checkin comments.

My thought was that anything safe for public consumption could be
prefixed with "cp:"(or whatever), but that might depend on how much
munging there is between your internal repo and Codeplex.

Or you could work off the Codeplex repo for real, and use a seperate
one for the sekrit stuff :).

- Jeff

More information about the Ironpython-users mailing list