Skip to content

Conversation

KristofferC
Copy link
Member

I think it is way too spammy right now. You precompile a set of packages and then have pages and pages of this warning. Don't think that is ok to introduce by default in a minor release. With the same argument that deprecation warnings are disabled by default, I think this should be as well.

@KristofferC KristofferC added the backport 1.12 Change should be backported to release-1.12 label Mar 25, 2025
@KristofferC KristofferC requested a review from Keno March 25, 2025 15:17
@Keno
Copy link
Member

Keno commented Mar 25, 2025

The backdating thing was supposed to be quite temporary - possibly even removed by 1.12 final, which is why we didn't put it under the depwarn flag originally. Are there any common patterns to these outdated accesses? It wasn't really supposed to be all that common to hit this.

This was referenced Mar 31, 2025
@KristofferC KristofferC mentioned this pull request Apr 29, 2025
53 tasks
@fingolfin
Copy link
Member

@KristofferC did you see @Keno's comment & question

(This also has a merge conflict by now :-/)

@KristofferC KristofferC mentioned this pull request May 9, 2025
58 tasks
@KristofferC KristofferC mentioned this pull request Jun 6, 2025
60 tasks
@KristofferC KristofferC closed this Jul 3, 2025
@KristofferC KristofferC removed the backport 1.12 Change should be backported to release-1.12 label Jul 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants