Fixed in r62193.
________________________________________
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Trent Nelson [EMAIL
PROTECTED]
Sent: 04 April 2008 20:41
To: "Martin v. Löwis"
Cc: Christian Heimes; python-dev@python.org
Subject: Re: [Python-Dev] r62129 - in python/trunk: PCbuild/debug.vsprops
PCbuild/kill_python.c PCbuild/kill_python.vcproj PCbuild/pcbuild.sln
PCbuild/pythoncore.vcproj PCbuild/release.vsprops Tools/buildbot/Makefile
Tools/buildbot/build-amd64.bat Tools/buildbo...
Ok, I'll change the approach this weekend.
Trent.
________________________________________
From: "Martin v. Löwis" [EMAIL PROTECTED]
Sent: 04 April 2008 19:57
To: Trent Nelson
Cc: Christian Heimes; python-dev@python.org
Subject: Re: [Python-Dev] r62129 - in python/trunk: PCbuild/debug.vsprops
PCbuild/kill_python.c PCbuild/kill_python.vcproj PCbuild/pcbuild.sln
PCbuild/pythoncore.vcproj PCbuild/release.vsprops Tools/buildbot/Makefile
Tools/buildbot/build-amd64.bat Tools/buildbo...
> What do others that do Windows development think? I don't have a
> problem changing the build behaviour if the approach I've taken is
> generally disliked.
I think kill_python should only ever be invoked in the build slaves;
it should *not* be part of the regular build. If developers find they
can't build because some files are still open, they should kill
the processes themselves.
Regards,
Martin
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/tnelson%40onresolve.com
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
