Remove stubs for pyvmomi (not until November 2023)

[hauntsaninja]

#10148

[intgr]

Just for information, I tried the upstream type hints and they are not usable yet. With the initial pyvmomi release shipping type stubs (8.0.1.0), there are syntax errors in a few of the files, preventing their use completely with mypy (vmware/pyvmomi#1015), and beyond that it looks like there will be other issues as well.

I'm sure the upstream stubs will improve over time, just need to wait some more. November deadline seems reasonable.

The upside is that upstream type stubs look like they're autogenerated and very extensive, they cover all of the API surface, not just a few object types like types-pyvmomi.

[AlexWaygood]

Ah, thanks for letting us know. If the upstream type hints are completely unusable, maybe it would be better to revert #10148 for now. (With the stubs marked as obsolete, the description on PyPI tells users not to use types-pyvmomi anymore, which is obviously incorrect advice right now: https://pypi.org/project/types-pyvmomi/.) This is a pretty unusual situation, though.

[AlexWaygood]

Okay, for now we've reverted marking the stubs as obsolete. We can mark types-pyvmomi as obsolete again once the upstream types are usable.

[intgr]

With the latest pyvmomi version 8.0.1.0.1 (May 25), the upstream type stubs work well with mypy for my use cases.

PyCharm still struggles with upstream types, but I have not investigated that in detail.

[AlexWaygood]

"Upstream types don't work perfectly with all type checkers" feels like it falls into the category of "the stubs are somewhat buggy" rather than "the stubs are fundamentally broken". So I'd vote for marking types-pyvmomi as obsolete once more, in that case. Thanks for the update @intgr!

[AlexWaygood]

Now marked as obsolete since 8.0.1.0.1: 2ec6ba9