Closed csuka closed 5 years ago
I submitted pull request #9 which should fix this issue
The real issue here is that the true "master" branch is pyspf-2_0-branch. This is an artifact of converting from CVS. I apologize for being such a git newbie, but I still haven't managed to get the branches renamed. I did make a pyspf-2.1 branch that was a copy of master - but I'm not sure what the next step is. I guess I should make a note of the situation in the README on the current "master".
OK, I didn't notice that. Thanks for clarification. maybe the best way to fix this is to merge pyspf-2_0 into master, getting the master branch updated with all patches/commits included in pyspf-2_0
git checkout master
git pull origin master
git merge pyspf-2_0
git push origin master
might be a way to do it...
I tried that. Notice the "merge pyspy-2_0-branch into master" commit - but I managed to screw it up. Fortunately, I saved master beforehand as the pyspf-2.1 branch.
I think the issue is doing a merge instead of "make this exactly like pyspf-2_0-branch".
Based on my newbie understanding of git, I would think I should be able to rename branches as well.
Changed:
raise spf.AmbiguityWarning, 'DNS: Truncated UDP Reply, SPF records should fit in a UDP packet, retrying TCP'
To
raise spf.AmbiguityWarning('DNS: Truncated UDP Reply, SPF records should fit in a UDP packet, retrying TCP')
To make it work on python3 on my setup.