[issue26469] Bug in ConfigParser when setting new values in extended interpolation

2016-03-02 Thread Michael Jacob
Michael Jacob added the comment: My bad. ConfigParser expects an interpolation object, not a class. Instead of c=ConfigParser(interpolation=ExtendedInterpolation) you need to create it with: c=ConfigParser(interpolation=ExtendedInterpolation()) Sorry about that. -- resolution

[issue26469] Bug in ConfigParser when setting new values in extended interpolation

2016-03-02 Thread Michael Jacob
New submission from Michael Jacob: There seems to be a bug in configparser when setting new values in extended interpolation: python --version Python 3.5.1 from configparser import ConfigParser, ExtendedInterpolation c=ConfigParser(interpolation=ExtendedInterpolation) c.add_section('test

[issue27749] multprocessing errors on Windows: WriteFile() argument 1 must be int, not None; OSError: handle is closed

2019-01-28 Thread Michael Jacob
Michael Jacob added the comment: Does this ticket track the issue in its title or the native crash? If it's the latter, is there a new ticket for the None _handle or shall I create one? -- nosy: +Michael Jacob2 versions: +Python 3.7 ___ Python

[issue27749] multprocessing errors on Windows: WriteFile() argument 1 must be int, not None; OSError: handle is closed

2019-01-31 Thread Michael Jacob
Michael Jacob added the comment: So, I'm experiencing the issue in the title, too. The pipe handle stays valid for between 5 and 60 minutes, then it goes None when written to. I'm far from understanding that code, but this crude re-connect code seems to solve the issue for me: In BaseProxy