Gereon Kremer added the comment:
Hm, I see.
For methods that do not intercept exceptions or run code in a different process
or alike, the deprecation warning and the TypeError should be sufficient.
Given that identifying this issue can be particularly nasty for setrlimit (if
used within
New submission from Gereon Kremer :
While the documentation always (as in: at least since 3.5) required to pass "a
tuple (soft, hard) of two integers" to resource.setrlimit(), passing floats
worked just fine until 3.9.
This behavior was deprecated in 3.8 and removed in 3.10.
I se
Gereon Kremer added the comment:
So, let's resurrect this one.
For the project that lead to the old patch, we did not need this feature.
However, we now needed are more complete implementation of IDLE.
Hence, we extended this to return after sending idle() and support polling,
leaving
Gereon Kremer added the comment:
I stumbled about this issue again and would really like to see it fixed.
I see the possibility to create a test case in combination with the first test
sequence which creates a temporary mail. Would it be enough, that we just call
IDLE in some folder, create a
Gereon Kremer added the comment:
I got the confirmation for my agreement.
I'm not quite sure about the tests, as I'm not really familiar with the way
this is done in cpython. The test_imaplib.py seems to cover all ways to connect
to some server, but none of the actual imap commands.
Gereon Kremer added the comment:
We have implemented this functionality according to RFC 2177.
We actually implemented a synchronous idle function that blocks until a timeout
occurs or the server sent some event.
This is not the most flexible way, however it will provide a basic
functionality
