Open
Conversation
fruffy
added
the
breaking-change
jafingerhut
approved these changes
Apr 8, 2026
Collaborator
jafingerhut
left a comment
jafingerhut
left a comment
There was a problem hiding this comment.
I hereby resolve to not mention again that backwards compatibility is very nice thing to preserve. :-)
Contributor
Author
Anyone that wants to keep using scapy can still do so by switching the module. We can also still add the warning and have one or two releases display it until we pull the trigger. Now with a consistent release cycle this really should not be a problem. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolve the issues that we provide the GPL scapy module with PTF.