Just a quick note that this bug has been fixed in pyasn1 master (commit https://github.com/etingof/pyasn1/pull/42/commits/2e5bbe62012c593d606c71e02131c8b7d0eeb2dd) and will appear in the upcoming pyasn1 release (the one past 0.2.3).
Just a quick note that this bug has been fixed in pyasn1 master (commit https:/ /github. com/etingof/ pyasn1/ pull/42/ commits/ 2e5bbe62012c593 d606c71e02131c8 b7d0eeb2dd) and will appear in the upcoming pyasn1 release (the one past 0.2.3).