-
Notifications
You must be signed in to change notification settings - Fork 76
Status of Scapy HTTP #46
Description
Hi,
Now that HTTP has been pushed back to the main Scapy repo (with quite a bunch of improvements/features/fixes for Python 3): secdev/scapy#1925 (or will be, if you're reading this before 2.4.3 😄), the question stands of what this project should do/become.
It is pretty clear that the project development has stopped:
Collaborator wanted!
Hi there, internet stranger! As time is a scarce resource for me nowadays, I'm looking for a collaborator to handle issues and pull requests in a more timely manner. If you are interested, send me an email at invernizzi.l@gmail.com.
(I wrote an email back in May but didn't get an answer).
The issue is that installing scapy_http will now break Scapy's implementation (http layer), rather than doing any good.
One option we have would be to deprecate it, and clearly raise a warning/error while installing. If this can't be done (no answer from the owners), the other option is that we (on Scapy) raise an error when it is installed.
I hope to get any feedback 😄