This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author zach.ware
Recipients brian.curtin, terry.reedy, tim.golden, zach.ware
Date 2013-03-10.06:31:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1362897098.29.0.261434521408.issue16895@psf.upfronthosting.co.za>
In-reply-to
Content
Here's an updated version in the form of a patch.

Features include:

- Ensure things are done in the right directory with pushd/popd

- Allow setting environment variables (for the life of the script) with:
     make test "PYTHON=..\PCbuild\python.exe"

- Emulate UNIX's `make -C <dir>` (cd dir; call make.bat %*, essentially)

- Choose x86 or x64 with "-64" command line switch

- Intelligently choose an interpreter for `make patchcheck` and `make test`

- Available targets are: build, clean, patchcheck, ready, test.  "ready" is implemented by Tools/buildbot/external[-amd64].bat; "make ready" sounds better and possibly more accurate than "make external" to me.

- Create a convenience "python.bat" script, which calls the newly built interpreter with all supplied arguments.  Created by :build, deleted by :clean (and added to .hgignore)


Everything seems to work ok for me, but my testing platforms are limited to a single Win7 laptop, currently.  This issue is also somewhat constrained by issue 17202; it is supposed to work without any change to .hgeol, but that can't be guaranteed.
History
Date User Action Args
2013-03-10 06:31:38zach.waresetrecipients: + zach.ware, terry.reedy, tim.golden, brian.curtin
2013-03-10 06:31:38zach.waresetmessageid: <1362897098.29.0.261434521408.issue16895@psf.upfronthosting.co.za>
2013-03-10 06:31:38zach.warelinkissue16895 messages
2013-03-10 06:31:37zach.warecreate