On Tue, May 13, 2008 at 9:09 PM, Jesus Cea <jcea at jcea.es> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I just committed pybsddb 4.6.4 to python svn. My next step (after a > successfull buildbot cycle, I hope!) is to commit the new testsuite. > First I need to review any changes there since I maintain pybsddb. > > The testsuite creates a lot of files/directories while working. Fine, > since it cleans later, unless some test crashes hard. My testcode > defines a variable to the path I want to use to keep those files/dirs. > Currently it is "/tmp/z-BerkeleyDB", or something like that. > > Since my code allows for testcases to be run in multiple threads and/or > processes, where would be a sensible path choice for temporal files?. > Current working directory would be fine, if "somebody" is cleaning after > running all tests. > It is up to the tests to clean up after themselves since they can be executed directly, so there is not magical location that gets cleaned up in case a test screws up. You can use test.test_support.TESTFN if you want a location. Or something from tempfile. -Brett
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4