[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._callmethod, I changed:

conn.send((self._id, methodname, args, kwds))

to:

try:
conn.send((self._id, methodname, args, kwds))
except TypeError:
self._connect()
conn = self._tls.connection
conn.send((self._id, methodname, args, kwds))

--

___
Python tracker 
<https://bugs.python.org/issue27749>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[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 tracker 
<https://bugs.python.org/issue27749>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[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:  -> not a bug
status: open -> closed

___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26469>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[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')
c.set('test', 'key', 'value')
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3.5/configparser.py", line 1190, in set
super().set(section, option, value)
  File "/usr/lib/python3.5/configparser.py", line 891, in set
value)
TypeError: before_set() missing 1 required positional argument: 'value'

It works ithout extended interpolation, though.

--
components: Library (Lib)
messages: 261101
nosy: Michael Jacob
priority: normal
severity: normal
status: open
title: Bug in ConfigParser when setting new values in extended interpolation
type: crash
versions: Python 3.5

___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26469>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com