pd.RangeIndex should accept range as the first argument

[kshitiz305]

• Closes pd.RangeIndex should accept range as the first argument #677 (Replace xxxx with the Github issue number)
• Tests added: Please use assert_type() to assert the type of any return value

[Dr-Irv]

Can you add a test to tests/test_indexes.py that instantiates a RangeIndex with a range argument, using check and assert_type as in other tests?

[kshitiz305]

Can you add a test to tests/test_indexes.py that instantiates a RangeIndex with a range argument, using check and assert_type as in other tests?

let me push the code with the required test.

[Dr-Irv]

@kshitiz305 checking on status of this PR

[kshitiz305]

@Dr-Irv Kindly have a look test for the range have been pushed

[Dr-Irv]

So there is a failure because pyright 1.1.309 started finding a whole bunch of issues. Trying to figure out what version to pin pyright to so things will work

[Dr-Irv]

Once #709 is merged, you will need to merge that in and revert changes to the 2 files I indicated.

[Dr-Irv]

@kshitiz305 #709 has been merged, so can you merge with main, fix the reported issues, and push, then we can run the tests to see if everything works

[Dr-Irv]

Please revert this change.

[twoertwein]

I think you can simply run git checkout <commit hash from before you made any changes> pandas-stubs/_version.pyi pyproject.toml to revert these two files to what they were before.

[Dr-Irv]

You also should do poetry run poe style before the next push, as the CI is failing because of that.

[kshitiz305]

@Dr-Irv commit 6d89c40

Could you help me with this if this shall include the new or __ init__ as this is leading a confusion and also failing pyright

[Dr-Irv]

This should be self, because it is in __init__()

I think this is the cause of the pyright error you are getting.

[Dr-Irv]

@kshitiz305 can you merge with main and get this finished up?