[issue40157] SMTP email policy does not encode non-ASCII characters

2020-04-02 Thread Eduard Bopp
New submission from Eduard Bopp : Using email.policy.SMTP a message's non-ASCII characters are not encoded. The policy.utf8 attribute is set to False as documented. The attached script illustrates the behaviour. I get the following command line output from it: Subject: =?utf-8?b?w7z

[issue14608] Python 2.7.3 x86 msi - msvcr90.dll version mismatch

2012-04-18 Thread Eduard
Eduard added the comment: > Any version should be fine. This is all I need to know. It's just one less place to check in case of troubles. Thank you for your time and patience. -- resolution: -> invalid status: open -> closed ___

[issue14608] Python 2.7.3 x86 msi - msvcr90.dll version mismatch

2012-04-17 Thread Eduard
Eduard added the comment: OTOH, the manifest embedded in python.exe references version 9.0.21022.8 I'm going to delete Microsoft.VC90.CRT.manifest and msvcr90.dll from Python installation folder and postpone py2exe experiments a bit. -- ___ P

[issue14608] Python 2.7.3 x86 msi - msvcr90.dll version mismatch

2012-04-17 Thread Eduard
Eduard added the comment: There is a newer redist available: 9.0.30729.6161 from http://www.microsoft.com/download/en/details.aspx?id=26368 -- ___ Python tracker <http://bugs.python.org/issue14

[issue14608] Python 2.7.3 x86 msi - msvcr90.dll version mismatch

2012-04-17 Thread Eduard
Eduard added the comment: I was reading about py2exe and found this old thread: https://groups.google.com/d/msg/wxpython-users/fwHt9zSbnsE/IV3aryIBrd8J I'm not familiar with C++ and redists and stuff, but I find it strange that the manifest from the Python folder requires a specific ve

[issue14608] Python 2.7.3 x86 msi - msvcr90.dll version mismatch

2012-04-17 Thread Eduard
New submission from Eduard : After installing Python 2.7.3, inside the Python folder I have version 9.0.30729.1 of msvcr90.dll, but it seems that the embeded redistributable package contains the 9.0.21022.8 version of msvcm90.dll, msvcp90.dll, and msvcr90.dll Is this the intended behavior