#5 too many value to unpack

[Nicolas Sebrecht]

Hi Piers,

The Request class set self.aborted to a 3 elements tuple but
IMAP4._command_completer asks to unpack only 2 values from it.

More details here:

https://github.com/OfflineIMAP/offlineimap/issues/173

I didn't dig into this more. I guess Request.abort_tb is right at
setting self.aborted = (typ, val, tb) and error unpacking is missing the
traceback.

This is still imaplib2 v2.37.

[Piers Lauder]

Hi Nicholas,

On Tue, 03 Mar 2015 12:00:58 +0000, Ticket 5 wrote:

---

** [bugs:#5] too many value to unpack**

Status: open
Group: v1.0_(example)
Created: Tue Mar 03, 2015 12:00 PM UTC by Nicolas Sebrecht
Last Updated: Tue Mar 03, 2015 12:00 PM UTC
Owner: nobody

Hi Piers,

The Request class set self.aborted to a 3 elements tuple but
IMAP4._command_completer asks to unpack only 2 values from it.

More details here:

https://github.com/OfflineIMAP/offlineimap/issues/173

I didn't dig into this more. I guess Request.abort_tb is right at
setting self.aborted = (typ, val, tb) and error unpacking is missing the
traceback.

I'm confused - there is no "abort_tb" method in imaplib2.py...?

Anyway, I'd like the code to be consistent with the manual which states that
the call back error value is a tuple (exception class, reason).

Is this by any chance an offlineimap ammendment?

This is still imaplib2 v2.37.

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/imaplib2/bugs/5/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[Piers Lauder]

closed, as this bug turned out to be in offlineimap ammendments