BUG: declare private str ufuncs as unsupported (np._core.umath._expandtabs*) - #16144

Thank you for your contribution to Astropy! 🌌 This checklist is meant to remind the package maintainers who will review this pull request of some common things to look for.

• Do the proposed changes actually accomplish desired goals?
• Do the proposed changes follow the Astropy coding guidelines?
• Are tests added/updated as required? If so, do they follow the Astropy testing guidelines?
• Are docs added/updated as required? If so, do they follow the Astropy documentation guidelines?
• Is rebase and/or squash necessary? If so, please provide the author with appropriate instructions. Also see instructions for rebase and squash.
• Did the CI pass? If no, are the failures related? If you need to run daily and weekly cron jobs as part of the PR, please apply the "Extra CI" label. Codestyle issues can be fixed by the bot.
• Is a change log needed? If yes, did the change log check pass? If no, add the "no-changelog-entry-needed" label. If this is a manual backport, use the "skip-changelog-checks" label unless special changelog handling is necessary.
• Is this a big PR that makes a "What's new?" entry worthwhile and if so, is (1) a "what's new" entry included in this PR and (2) the "whatsnew-needed" label applied?
• At the time of adding the milestone, if the milestone set requires a backport to release branch(es), apply the appropriate "backport-X.Y.x" label(s) before merge.

Note that there are more to come...

One byte at a time 😄

I've merged this despite the-dev job not passing since this is quite obviously correct, and we know where the trouble is with -dev.

@mhvk I think you forgot the backport label. I'll do it manually.

update: #16145

Is there a follow-up issue for the current numpy-dev failure?

astropy/units/quantity.py:829: in _new_view
    obj = np.array(obj, copy=False, subok=True)
E   ValueError: Unable to avoid copy while creating an array.

Update: Ah, nvm, I see #16142

yeah, I naively thought the patch would be trivial so I didn't open an issue for it. Now that the situation is clearer, I'm planning to open a long term issue for what's next !