#338 closed enhancement (invalid)

windows-exe requirement check

Reported by: zooko Owned by: robk
Priority: major Milestone: eventually
Component: packaging Version: 0.8.0
Keywords: install windows setuptools Cc:
Launchpad Bug:


It would be nice if the "make windows-exe" make target would error out if it is unable to import a require module. We just lost a lot of time because I had reinstalled setuptools on the Windows buildslave, and I didn't know that one needed to install setuptools with the --always-unzip option so that py2exe would be able to pull in pkg_resources, and the process of us figuring out what was wrong with the resulting Windows executable took a long time.

Change History (3)

comment:1 Changed at 2008-03-10T22:58:27Z by zooko

This is related to a recent topic regarding several different packaging patches: how does one automatically test a patch that changes your packaging scheme? It would be great if there were a "PrivateInstallAndTest?" buildbot buildstep which installs into a local, newly created install directory from the resulting package, and then runs the unit tests from that installation.

See #335 (OSError when trying to access http://localhost:8123/provisioning/), which has links to other issues in Nevow, Twisted, and Tahoe along these lines.

comment:2 Changed at 2009-12-12T02:39:36Z by davidsarah

  • Keywords install windows setuptools added

comment:3 Changed at 2011-01-03T02:41:12Z by davidsarah

  • Resolution set to invalid
  • Status changed from new to closed

Obviated by removal of the Windows app in #1282. Also, we do now have several build steps that test packaging.

Note: See TracTickets for help on using tickets.