Inconsistent behavior of Session initializers

[tachikoma-li]

Describe the bug

When creating a Session from id using Session.from_id, a deprecation warning is raised if one passes a backend argument. However, if one doesn't pass a backend, the default Session initializer (which is called from Session.from_id) would raise another deprecation warning or error.

It's not clear what's the expected behavior from the docs. Might be good to make the two initializers consistent.

If the default Session initializer now does require backend, it might be also good to update the type hints and the docs of the backend parameter.

*Steps to reproduce

Expected behavior

Suggested solutions

Additional Information

• qiskit-ibm-runtime version: 0.22.0
• Python version: 3.11
• Operating system: macOS Sonoma

[kt474]

Hi @tachikoma-li - there is an open PR for updating the from_id method (#1311). It will take care of the inconsistencies you have mentioned here.

[tachikoma-li]

@kt474, nice to see it's tracked. Hopefully this could be addressed in the next release.

Closed as there is already a PR on it.

[kt474]

@kt474, nice to see it's tracked. Hopefully this could be addressed in the next release.

Closed as there is already a PR on it.

We will try to have it in before the next release

[kt474]

#1311 Has been merged, it'll be in the next release, planned for this Monday