lucene-pylucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Koch" <>
Subject AW: AW: AW: [VOTE] Release PyLucene 4.2.1-1
Date Mon, 22 Apr 2013 11:06:06 GMT
> Thanks again. A trick - on Windows - might be to rename the testrepo dir
> testrepo.<current datetime> and move to the next test. And clean them all
> up at the end. Or create a testrepos directory tree where each
> testrepo.<currentTime> is going to be created and remove the whole tree at
> the end.

Sure, that's similar to what I did for the test_PyLucene (in

> > I then ended up in using a 'fresh' test-repository (i.e. new dir name)
> > if rmtree fails. The test_PyLucene test then passes on windows - the
> > downside is that you end up with some testrepo.1, testrepo.2 etc. dirs
> > - and of course an attempt to cleanup these dirs after
> > unittest.main(exit=False) also fails...

Problem here is that one cannot cleanup the testrepos while inside the test
loop. It must be done outside, i.e. on Makefile level (well on windows

> GIven that Lucene 4.3 is about to be released, I think I'm going to drop
> 4.2.1 PyLucene release and move to proposing a PyLucene 4.3 release
> candidate next.

Is there a release date yet? Saw something on twitter, but not on the
website and JIRA still states a number of open issues:


View raw message