Jeff McNeil added the comment:
Updated to recalculate timeout at Python level. The current module already
works this way on recv() calls. See attached.
I'd be happy to churn through and fix the other modules (using the 3.5 work as
a guide), though I think only addressing the higher
Jeff McNeil added the comment:
Added a flag to allow for at least one run -- I know nothing of non-Linux clock
resolution. That should handle that.
As for the thread safety of the socket timeouts, yeah, that was why I didn't do
that initially, I assumed the suggestion to take that app
Jeff McNeil added the comment:
Actually, never mind that suggestion. Now that I think a bit more about it,
that actually doesn't do anything since I'd still need to set the updated
timeout on the current socket object anyway. Whoops.
I'll leave it up to you as to whethe
Jeff McNeil added the comment:
I'm not a big fan of the settimeout approach myself (and only did it because it
was mentioned as a possible approach). I think the existing implementations of
EINTR retry also suffer from the same issue in which the timeout isn't adjusted
per iter
Jeff Ramnani added the comment:
So, the devguide has been updated since this issue was opened. The Quick Start
section now has a link to build documentation, which includes information about
build dependencies. Is this sufficient to call this bug closed?
--
nosy: +jramnani
Jeff McNeil added the comment:
Fixing the underlying connect call should also address EINTR failing with a
"operation already in progress" when a connect+timeout fails due to a signal.
I can understand not addressing EINTR generically (though it is already
partially addresse
Jeff McNeil added the comment:
Do we have a decision on this yet? I'm willing to rework bits that may need
it, but I'd like to know whether this is going to be a fruitful effort or not.
Thanks!
--
___
Python tracker
<http://bu
New submission from Jeff Ding:
After uninstalling old versions of Python:
Python is unable to install unless I disable pip.
Once python installs, python immediately crashes due to Py_Initialize
--
components: Windows
files: python_crash.png
messages: 244003
nosy: Jeff77789
New submission from Jeff Reback:
xref to https://github.com/pandas-dev/pandas/issues/14679.
pandas has had a cython extension class to datetime.datetime for quite some
time. A simple __reduce__ is defined.
def __reduce__(self):
object_state = self.value, self.freq, self.tzinfo
Jeff Reback added the comment:
ok thanks for the info. fixed in pandas here:
https://github.com/pandas-dev/pandas/pull/14689
is this documented in the whatsnew?
--
___
Python tracker
<http://bugs.python.org/issue28
301 - 310 of 310 matches
Mail list logo
