Closed dajose closed 6 years ago
Sorry for the confusion, we are in a bit of a turmoil going through renaming. Let me explain: the whole project and subsequent PyPI packages (and python module itself) are being renamed to kamene. Thus from now on you have to install it pip3 install kamene
and import it as from kamene.all import *
. The first release implementing the renaming is v0.31.
v0.24 is an intermediate release to display warning message that further development will be under different name. It is the last one being published on PyPI as scapy-python3 package. version space between v0.24 and v0.31 is reserved for bug fixing or additional information messages for people currently using scapy-python3.
One more note - unless you have specific reasons to do otherwise, I recommend migrating directly to kamene (v0.31 and up) using new package name (i.e. installing kamene from PyPI), and uninstalling scapy-python3.
oh, but I think v0.24 would not work as you intended, as the name of the module was changed to scapy3k. So, it will not give a warning but fail at import.
The package file on PyPI had an issue, just fixed it. If using scapy-python3 PyPI (v0.25 latest) then import scapy... should work, when using kamene from PyPI, then import kamene... should work. Anyway, the whole intent of updating scapy-python3 package was just to add notification message, it is not going to be updated.
:) that's what we needed here. Thanks :)
We'll update to kamane in the future
Hi, I'm not very familiar with the renaming schema you guys are doing... but I'm confused with the transition naming change on latest 0.24 release to scapy3k.
what's the intention there? also, The git tag for that release doesn't match the code that is downloadable on pypi.