Allow bypassing log setup in the API use

[whg517]

In my code, I wanted to create the virtual environment manually by calling def cli_run(args, options=None): , but when I ran it, I found that my log could not be obtained. Through searching, I found that you clarified the root log in the code, which made me unable to use my log object after running.

I wonder what you're doing this for? Do you use custom Log objects instead of cleaning the root Log ?

virtualenv/src/virtualenv/report.py

Line 39 in 16f80ac

LOGGER.setLevel(logging.NOTSET)

virtualenv/src/virtualenv/report.py

Lines 48 to 50 in 16f80ac

	def _clean_handlers(log):
	for log_handler in list(log.handlers): # remove handlers of libraries
	log.removeHandler(log_handler)

I now can do a patch or duplicate the code of cli_run, session_via_cli, and build_parser and remove the line _do_report_setup .

[gaborbernat]

We're using our own log reporters to guarantee output, without clearing the logs we might generate our output in unwanted locations. For your use case, I think would be helpful to have an option to disable log setup. Though now one might argue that the output controlling flags would be unrespected.

[whg517]

Thank you for your reply. I understand what you mean.

If you want to avoid this, I think you can readjust the invocation logic to leave the interfaces for third-party applications. Not as tightly coupled

In fact, I think the upper layer of the function module should be the CMD call layer in the design. When other projects need to use it, the corresponding function module can be directly used.

Of course, given that Virtualenv is already a mature scenario, I've only been thinking about it by looking at its source code, perhaps prematurely. Please don't mind.

In my current practice, I copied three methods cli_run , session_via_cli and build_parser from virtualenv/run/__init__.py , then deleted _do_report_setup(parser, args) in build_parser method.

You can also do this through a Subprocess call, but it may take more work on process control and exception handling.

Of course I wish there was a more elegant way to solve this problem. Thank you again.