[issue10572] Move unittest test package to Lib/test

Brett Cannon added the comment: I have no issue with moving importlib into Lib/test as long as I can still run the tests with ``python3 -m test.importlib``. I actually only put the tests in importlib.tests because that was common practice amongst newer packages in the stdlib. And just to pre

[issue10572] Move unittest test package to Lib/test

Raymond Hettinger added the comment: Of those, it makes the most sense to move the json tests to Lib/tests. Bob is not externally maintaining the 3.x version. It's all our now. Also, it looks like importlib is in a maintenance mode now. There is merit to keeping 2to3, ctypes, sqlite tests s

[issue10572] Move unittest test package to Lib/test

Éric Araujo added the comment: For distutils tests, I’m ±0. I don’t see any major drawback nor any major benefit. Tarek will decide. -- ___ Python tracker ___ ___

[issue10572] Move unittest test package to Lib/test

R. David Murray added the comment: Yes, a cheeseshop package is definitely part of the plan, I didn't mean to imply otherwise. It won't be hard to automate the packaging, and indeed I'll wind up doing that anyway even if the tests stay inside Lib/email. I will say that that I'm probably only

[issue10572] Move unittest test package to Lib/test

Barry A. Warsaw added the comment: grepping the code without the tests doesn't seem that compelling a use case to me, given that grep and find both provide options to prune directories. I do think that moving the tests out of the email package will make it harder to maintain and distribute a

[issue10572] Move unittest test package to Lib/test

R. David Murray added the comment: For the email package I would be in favor of moving the tests to Lib/test. I've always found it a bit inconvenient that they are in Lib/email. After hearing of Michael's intent with unittest, and given the evolution of email5 into email5.1, I am also consi

[issue10572] Move unittest test package to Lib/test

Changes by Alexander Belopolsky : -- nosy: +gpolo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue10572] Move unittest test package to Lib/test

Michael Foord added the comment: That list of examples was non-exhaustive, there is also tkinter. -- ___ Python tracker ___ ___ Pytho

[issue10572] Move unittest test package to Lib/test

Alexander Belopolsky added the comment: +0, and I think we should hear from the maintainers of the affected packages first. For packages that are also externally maintained moving tests out may cause inconvenience to the maintainer. -- nosy: +barry, belopolsky, brett.cannon, ghaering

[issue10572] Move unittest test package to Lib/test

Michael Foord added the comment: The same is true for 2.7 though, and that is getting bug fixes. svnmerge would no longer work (and to making the change would mean moving the tests in a point release). -- ___ Python tracker

[issue10572] Move unittest test package to Lib/test

Ezio Melotti added the comment: 3.1 should also be considered if the tests are moved. In theory this is not a bug fix so it shouldn't go in 3.1, but in practice it will make merging more difficult. This might not be a strong argument though, considering that 3.1 will accept only security fi

[issue10572] Move unittest test package to Lib/test

Changes by Éric Araujo : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue10572] Move unittest test package to Lib/test

New submission from Michael Foord : Having tests in Lib/test instead of inside the package makes it easier to grep the unittest package without grepping the tests. The Windows installer has an "install without tests" option which is easier to honour if the tests aren't in the package. However