Joaquin Alzola <joaquin.alz...@lebara.com> writes: > I suppose a SW that is going to live will not have any trace of > unittest module along their code.
Many packages are deployed with their unit test suite. The files don't occupy much space, don't interfere with the running of the program, and can be helpful to run the tests in the deployed environment. > So is it the way to do it to put all unittest in a preproduction > environment and then remove all lines relate to unittest once the SW > is release into production? I would advise not to bother. Prepare the release of the entire source needed to build the distribution, and don't worry about somehow excluding the test suite. > This email is confidential and may be subject to privilege. If you are not > the intended recipient, please do not copy or disclose its content but > contact the sender immediately upon receipt. Please do not use an email system which appends these obnoxious messages in a public forum. Either convince the people who impose that false disclaimer onto your message to stop doing that; or, stop using that system for writing to a public forum. -- \ “Are you pondering what I'm pondering?” “Umm, I think so, Don | `\ Cerebro, but, umm, why would Sophia Loren do a musical?” | _o__) —_Pinky and The Brain_ | Ben Finney -- https://mail.python.org/mailman/listinfo/python-list
