-
Notifications
You must be signed in to change notification settings - Fork 18
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
Warning spam from pybnf dependencies #274
Comments
Since we have a recurring issue of new package updates producing new unwanted output, it would be really nice to permanently solve this by suppressing all output except that generated by our printing module. |
+1 to needing to fix the general case. Best case scenario would be to send stderr to the log instead of the terminal. |
@emitra17 can I take this up ? I'd love to contribute to the repository and this seems like a good place to start. |
Your help with this would be appreciated!
…Sent from my iPhone
On Dec 17, 2021, at 9:13 AM, Saurav Maheshkar ***@***.***> wrote:
@emitra17 can I take this up ? I'd love to contribute to the repository and this seems like a good place to start.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.
|
I ran |
I'm not sure why using the -e option would matter.
I wonder if Jacob (cc'ed) fixed the issue but didn't close it.
…On Mon, May 16, 2022 at 12:35 PM Saurav Maheshkar ***@***.***> wrote:
I ran pip install -U pybnf on a fresh colab instance and didn't see any
of the aforementioned errors. Do these errors come up during editable
installs ?
—
Reply to this email directly, view it on GitHub
<#274 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AETOR53CZ2ZMKJDU7H2CETDVKKIQTANCNFSM4HDMVLYA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Using fresh versions of all dependencies, with normalization enabled, the terminal gets spammed with many copies of the warning "data.py:304: RuntimeWarning: invalid value encountered in true_divide", presumably from a divide by 0 for some parameter sets.
The text was updated successfully, but these errors were encountered: