-
Notifications
You must be signed in to change notification settings - Fork 242
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
Importing BCBio.GFF suppresses Biopython warnings in external code #140
Comments
It's possible this will not get merged for a while given how quiet this repo is. Is there a way to undo the warnings silencing? E.g. after importing BCBio.GFF one runs something like:
|
@corneliusroemer yes, I've added that in nextstrain/augur@05bff35. Note that it has to come not just after importing BCBio.GFF, but all usages of it that emit Biopython deprecation warnings. |
Closed by 03e96ca. |
@chapmanb thanks so much for releasing 0.7.1 and continuing to maintain bcbio-gff which continues to be widely used in production at e.g. Nextstrain |
bcbb/gff/BCBio/GFF/GFFParser.py
Lines 46 to 47 in 81442c0
The above lines may have been added with good intents to reduce unnecessary outputs. In practice, it has hidden important messages from users, causing deprecations to be noticed only when it's too late:
What's worse is that this warning suppression affects everything in the same Python process, even outside of BCBio code. Example with Biopython 1.81:
The text was updated successfully, but these errors were encountered: