python 2.7 no longer supported with str(x,y) syntax added in 1.1.0

Bug #2008738 reported by Bo Bleckel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dkimpy
Fix Released
Medium
Scott Kitterman

Bug Description

When 1.1.0 was released, there was no mention of dropping Python 2.7 support. Now I know that we should have dropped that long ago, and we mostly have, but as it turns out, one app that we still support makes use of the dkimpy library and still supports python 2.7. We noticed in our weekend build that the newest version of the library uses a syntax that isn't supported by Python 2.7:

Line 303, in validate_signature_fields

    str(sig[b'd'], 'ascii')

TypeError: str() takes at most 1 argument (2 given)

It is totally fine if the package no longer supports Python 2.7 (I personally think that is probably the right approach), but then the 1.0.x version would be pulled in as the latest 2.7 supported version. That would be fine by us. It is a problem, however, for a version to be released with python 2.7 incompatible syntax but still purport to support 2.7.

Just some clarity would be appreciated! Thanks!

Revision history for this message
Scott Kitterman (kitterman) wrote :

I agree it should be documented. I'll fix that in the next update. Thanks.

Changed in dkimpy:
status: New → Triaged
importance: Undecided → Medium
milestone: none → 1.1.1
Revision history for this message
Scott Kitterman (kitterman) wrote :

Documentation is updated in git.

Changed in dkimpy:
status: Triaged → Fix Committed
assignee: nobody → Scott Kitterman (kitterman)
Changed in dkimpy:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.