From: SourceForge.net <no...@so...> - 2006-06-02 13:01:00
|
Bugs item #654957, was opened at 2002-12-17 02:43 Message generated for change (Comment added) made by ghaering You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=654957&group_id=16528 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Documentation Group: None >Status: Closed >Resolution: Wont Fix Priority: 3 Submitted By: Gerhard Häring (ghaering) Assigned to: Billy G. Allie (ballie01) Summary: How to run test suite? Initial Comment: A MacOS X user whom I was assisting getting pyPgSQL 2.3 to work on his machine was telling me that the instructions in the README about running the test suite don't work for him. In fact, they can't work because "python test/PgSQLTestCases.py" won't work if you built pyPgSQL with "... setup.py build" before. I personally just copy the test directory with a "cp -r ..." to build/lib.{platform}" but I wonder what you do during development? There's the possibility to use a "python setup.py build --build-lib ." instead, with which the instructions in README would work. I personally don't do this because it clutters up my pyPgSQL sandbox. If you know how to change the instructions, could you please do so? Thanks. ---------------------------------------------------------------------- >Comment By: Gerhard Häring (ghaering) Date: 2006-06-02 15:00 Message: Logged In: YES user_id=163326 Deferred. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=654957&group_id=16528 |