Switch pandas stubs to the ones maintained by pandas team

[gramster]

This is not something we can do yet (as I write this), but the pandas team are going to take over stub maintenance at some point and move them to a package on PyPI.

Meanwhile, we need to decide what to do about open issues we have for our stubs. @Dr-Irv, do you have an insight into the timeline and should we still fix issues here?

[Dr-Irv]

I've started the process of creating a repo in the pandas project, and have to do a bit more work before we can decide to publicize it. It's somewhat dependent on my time to do this work. I would hope that by the end of June we have a public repo.

I think we should continue to fix issues here so that people using the MS shipped stubs get fixes as they identify the need, since you're doing new releases in VS Code on a weekly basis.

As changes happen here for the pandas stubs, I'll copy them over to the repo I've created over in the pandas project (which is currently private - visible to the pandas core team)

[Dr-Irv]

The repo is now public: https://github.com/pandas-dev/pandas-stubs

[alkatar21]

Since #208 has been merged. Is there already a date when the first pylane release with the new pandas stubs will be published?

[alkatar21]

@Dr-Irv @gramster According to python-in-visual-studio-code-june-2022-release, the stubs from https://github.com/pandas-dev/pandas-stubs are now used, but in pylance v2022.6.10 at least pandas-dev/pandas-stubs#15 (#199) seems to be missing and I can't find it in https://github.com/microsoft/pylance-release/blob/main/CHANGELOG.md either.
Are there any further information, or should I create an issue in the pylance repo?

[Dr-Irv]

@alkatar1 I have nothing to do with the pylance releases, so hopefully @gramster can answer. Or @luabud who wrote that blog.

[gramster]

Will be fixed in next release (likely today); the blog post jumped the gun a bit.