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

Suppress spurious compiler warnings on first import of omas #289

Open
hassec opened this issue Feb 12, 2024 · 7 comments
Open

Suppress spurious compiler warnings on first import of omas #289

hassec opened this issue Feb 12, 2024 · 7 comments
Labels

Comments

@hassec
Copy link
Contributor

hassec commented Feb 12, 2024

On first import of omas, the compilation of the cython extensions will dump a ton of warnings.
See e.g.:
image

And this continues for O(100) lines. IMHO this is quite confusing for new users.

It would be nice if there was a way to suppress these or even better build extensions as part of the packaging to in addition to avoiding these warnings, one also avoids the slowdown on the first import.

Copy link

Stale issue message

@hassec
Copy link
Contributor Author

hassec commented Apr 20, 2024

The stale issue bot is a bit too quick to close issues IMHO...

@orso82 could you reopen?

@hassec
Copy link
Contributor Author

hassec commented Apr 23, 2024

@jmcclena @AreWeDreaming @torrinba could one of you reopen this issue?

Copy link

This issue has not seen any activity in the past 60 days. It is now marked as stale and will be closed in 7 days if no further activity is registered.

@hassec
Copy link
Contributor Author

hassec commented Jun 23, 2024

@orso82 could we mark this as bug so it doesn't get closed by the stale bot?

@orso82
Copy link
Member

orso82 commented Jun 23, 2024

sure, go for it!

@hassec
Copy link
Contributor Author

hassec commented Jun 23, 2024

I do not have the rights to do that 😁

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

Successfully merging a pull request may close this issue.

3 participants