Guido van Rossum wrote: >>I've been having trouble running the tests lately, because test_pwd is >>really slow. It's a fairly trivial set of tests -- checking the types >>of return values and cross-checking getpwall() vs. >>getpwnam()/getpwuid(). The problem is if your password database is >>provided by LDAP and is really big, the test takes an impractically >>long time. >> >>Would anyone object if I changed the test suite to require some >>resource to run test_pwd? Or should I just make some local change to >>disable it? > > > How about instead limiting the number of entries checked to the first > 100? Try changing > > entries = pwd.getpwall() > > into > > entries = pwd.getpwall()[:100] If the bottleneck is in the n calls to pwd.getpwnam() and pwd.getpwuid() limiting n is an option. If the bottleneck is the one call to pwd.getpwall() adding a resource requirement might be the only option. Bye, Walter Dörwald
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