[issue35149] pip3 show causing Error for ConfigParaser

Eryk Sun added the comment: In Windows, Python defaults to the system ANSI codepage (e.g. 1252 in the West) for non-console standard I/O. For the case of a `for /f` loop in CMD, stdout is a pipe, so Python defaults to writing ANSI encoded text to its end of the pipe. I recommend overriding

[issue35149] pip3 show causing Error for ConfigParaser

Karthikeyan Singaravelan added the comment: I am able to reproduce this by explicitly setting PYTHONIOENCODING as ascii . But I am not sure about the defaults in Windows (related to your environment, os only?) and perhaps something has changed since 3.6 since it fails when executed under

[issue35149] pip3 show causing Error for ConfigParaser

Karthikeyan Singaravelan added the comment: Sorry I overlooked the part where it says this works with command line but throws an error on batch script. -- ___ Python tracker

[issue35149] pip3 show causing Error for ConfigParaser

Karthikeyan Singaravelan added the comment: Thanks for the report. The tracker is for issues related to CPython. I think this is an issue with pip and please file an issue at https://github.com/pypa/pip/issues. I can see some related issues as per your original report on googling

[issue35149] pip3 show causing Error for ConfigParaser

New submission from Dileep : I' receiving error while viewing the package info of ConfigParser. The command `pip3 show ConfigParser` doesn't cause any error where as following batch script is resulting this error It has something to do with Autor name or Unicode handling of the Pip3 `for /f