# Duplicated stdout and input call leads to 'Logger' object has no attribute 'errors' **URL:** \ **Category:** Python Help\ **Created:** [December 8, 2021, 3:59pm UTC](https://discuss.python.org/t/duplicated-stdout-and-input-call-leads-to-logger-object-has-no-attribute-errors/12419 "2021-12-08T15:59:31Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![fredP](https://avatars.discourse-cdn.com/v4/letter/f/8c91f0/32.png) [@fredP](https://discuss.python.org/u/fredP)\ **Post date:** [December 8, 2021, 3:59pm UTC](https://discuss.python.org/t/duplicated-stdout-and-input-call-leads-to-logger-object-has-no-attribute-errors/12419/1 "2021-12-08T15:59:31Z")
Hello Hard to summarize my issue in title… I recovered an old project, written with python2, upgraded it to python 3.4 (blocked by my OS: SLES12SP5), all was good… until I tried to “enhance” a display. In application, stdout is duplicated for taking all traces in console and a file, it’s still from old code in python2 I think: ```auto import log sys.stdout = log.Logger(sys.stdout, "install.log") ``` The point to enhance is an user input, asked with a “nice\_input” function: ```auto def nice_input(question, validate=None): """ Ask for text input :param question: Question text :param validate: Validation method :return: the user input """ if validate is not None: questions = [ inquirer.Text('response', message=question, validate=validate), ] else: questions = [ inquirer.Text('response', message=question), ] answers = inquirer.prompt(questions) return answers['response'] ``` At this point, the display disappointed me : if user enters a wrong entry, the question is displayed again with the entry. If user uses the backspace, display is not erased and only cursor moves. With a “shift + backspace”, characters are well erased. So I tried a more logic method I think (and with better display) : ```auto while True: backup_file_name = input("Backup file name: ") if is_a_valid_filename(backup_file_name): break ``` but… an error occurs on the ‘input’ (I tried a simple ‘input’ call and error occurs) : AttributeError: ‘Logger’ object has no attribute ‘errors’ I’m trying to change the way that stdout is duplicated to a file (with logging module or this method : ```auto class Logger(object): def __init__ (self): self.terminal = sys.stdout self.log = open("logfile.log", "a") def write(self, message): self.terminal.write(message) self.log.write(message) def flush(self): # this flush method is needed for python 3 compatibility. # this handles the flush command by doing nothing. # you might want to specify some extra behavior here. pass sys.stdout = Logger() ``` ) but without success. The following error occurs: File “install.py”, line 180, in firewall2.reload() File “/tmp/app/data/firewall2.py”, line 93, in reload subprocess.check\_call(["/sbin/SuSEfirewall2"], stdout=sys.stdout, stderr=sys.stdout) File “/usr/lib64/python3.4/subprocess.py”, line 553, in check\_call retcode = call(\*popenargs, \*\*kwargs) File “/usr/lib64/python3.4/subprocess.py”, line 534, in call with Popen(\*popenargs, \*\*kwargs) as p: File “/usr/lib64/python3.4/subprocess.py”, line 820, in **init** errread, errwrite) = self.\_get\_handles(stdin, stdout, stderr) File “/usr/lib64/python3.4/subprocess.py”, line 1305, in \_get\_handles c2pwrite = stdout.fileno() AttributeError: ‘Logger’ object has no attribute ‘fileno’ As I said, it’s an old project with some thousands lines code… hope I could avoid changing a lot of interactions with I/O streams. Any advice on the way to solve this kind of problem ? maybe an issue on stdin as the ‘input’ function leads to the error ? ---
**Author:** ![CAM-Gerlach](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/cam-gerlach/32/3688_2.png) [@CAM-Gerlach](https://discuss.python.org/u/CAM-Gerlach)\ **Post date:** [December 9, 2021, 5:53am UTC](https://discuss.python.org/t/duplicated-stdout-and-input-call-leads-to-logger-object-has-no-attribute-errors/12419/2 "2021-12-09T05:53:49Z")
Just FYI, Python 3.4 was released over seven and a half years ago, and has been end of life upstream for well over two and a half years. Few modern packages support it anymore, and many never did in the first place. In any case, if you want a logger that logs both to a file and to `stdout`, there is no need for aweful hacks. Instead, simply add two handlers, one for logging to stdout, and one for logging to a file. See the first few lines of the official [logging cookbook](https://docs.python.org/3/howto/logging-cookbook.html#logging-cookbook). Here’s an abridged version with just the parts most relevant to your issue: ```python import logging import sys # Create logger for 'spam_application' logger = logging.getLogger('spam_application') # Create file handler fh = logging.FileHandler('install.log') # Create console handler ch = logging.StreamHandler(sys.stdout) # Add the handlers to the logger logger.addHandler(fh) logger.addHandler(ch) ``` Cheers! ---
**Author:** ![fredP](https://avatars.discourse-cdn.com/v4/letter/f/8c91f0/32.png) [@fredP](https://discuss.python.org/u/fredP)\ **Post date:** [December 9, 2021, 9:16am UTC](https://discuss.python.org/t/duplicated-stdout-and-input-call-leads-to-logger-object-has-no-attribute-errors/12419/3 "2021-12-09T09:16:31Z")
Thanks for the tips, I already tried something like that but I’ll try again. In fact, it’s an old project, I have to maintain it before making any global change (as changing for a newer version for python…) and, as I’m a new python user, I have to go step by step. The main advantage I see in proceeding this way on an old project, is to understand the mechanisms related to python.