diag still read-only #7661

Activity

1. shoyer commented on May 23, 2016

   

   shoyer

   on May 23, 2016

   Member

   More actions

   We put off making this change in 1.10 after getting some significant pushback. See this blog post and the subsequent mailing list discussion (which could be turned up with some searching) for more details.
2. akhmerov commented on May 23, 2016

   

   akhmerov

   on May 23, 2016

   Author

   More actions

   Do you mean this discussion?

   It seems to conclude with something like:

   I would love to do the PR once a decision is reached.

   Perhaps now, almost 1.5 years after the last posts in that discussion and more than 2 years after the release of v1.8 it could be a good time to re-raise the topic. Maybe it's time to do the change it in 1.12?
3. shoyer commented on May 23, 2016

   

   shoyer

   on May 23, 2016

   Member

   More actions

   Yes, that looks like the right discussion. It does look like it petered out without a resolution -- I would suggest re-raising it on the mailing list.
4. ahaldane commented on Jul 6, 2016

   

   ahaldane

   on Jul 6, 2016

   Member

   More actions

   PR #6054 implements a deprecation warning for this change, by the way. The idea would be to warn in 1.12, then implement in 1.13.
5. rgommers commented on May 8, 2021

   

   rgommers

   on May 8, 2021

   Member

   More actions

   Closing as a duplicate of gh-5407.
6. rgommers

   closed this as completedon May 8, 2021