Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to hide warnings? #225

Open
taoxinyi opened this issue Nov 28, 2017 · 5 comments
Open

How to hide warnings? #225

taoxinyi opened this issue Nov 28, 2017 · 5 comments

Comments

@taoxinyi
Copy link

WARNING: can't import layer can: No module named 'fcntl'
WARNING: Unless called manually, this could indicate deprecated use. Should be changed to bytes(self)
WARNING: more Unless called manually, this could indicate deprecated use. Should be changed to bytes(self)

How to hide and suppress such warnings?

@GhostofGoes
Copy link

GhostofGoes commented Dec 11, 2017

import warnings
warnings.simplefilter("ignore")

Or when you run Python: python -W ignore script.py

Source

Many libraries make use of this module, so if you're shipping a user-facing terminal app it's useful to disable them unless you're debugging.

@gpotter2
Copy link

Hi !

This issue has been resolved on the original scapy fork, which now supports Python 3 !
This fork (scapy3k) is missing many updates, bug fixes and tweaks. You can have a look at
https://github.com/secdev/scapy to get more support !

Have a good day

@GhostofGoes
Copy link

The original does not yet support Python 3 in the full release, only the release candidates AFAIK.

@phaethon
Copy link
Owner

Dear @gpotter2 could you provide a patch or point to specific commit? For the people valuing code tested in production for 2+ years over release candidate.

@GhostofGoes
Copy link

@gpotter2 Please don't post the same copy-paste comment in every issue on this repo. If the information is relevant to all, open a separate issue. The rc branch isn't done magical cure-all for every bug in this fork, unless I'm mistaken.

And apologies on posting comments unrelated to the issue. Didn't know where else I should address the comment spam that filled my motivations this evening.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants