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.

Sign up for GitHub

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

Jump to bottom

Where did the caveats section go? #41

Closed
carstenbauer opened this issue Apr 18, 2020 · 4 comments
Closed

Where did the caveats section go? #41

carstenbauer opened this issue Apr 18, 2020 · 4 comments

Comments

@carstenbauer
Copy link
Member

carstenbauer commented Apr 18, 2020 •
edited
Loading

I remember there was a caveats section in the Readme.md. I can't find it anymore. I doubt that the caveats are gone - please correct me if I'm mistaken. So why has it been removed and what are the current shortcomings of MKL.jl?
@carstenbauer
Copy link
Member Author

carstenbauer commented Apr 18, 2020 •
edited
Loading

I see #17 but new caveats section has not been added yet.

Python interoperatability is still an issue, isn't it?

Of course, it would also be great to mention things like MKL.enable_openblas_startup() in the Readme.

@aminya
Copy link
Contributor

aminya commented Apr 18, 2020

They got solved. #35 also solves the Python problem.

@carstenbauer
Copy link
Member Author

That's great news. However, it seems there are some (minor?) side effects, which is why I asked in #35 for clarification of what those are.

@ViralBShah
Copy link
Contributor

Let's have a new issue if the registered package needs caveats mentioned in the README.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@carstenbauer @ViralBShah @aminya