refactor(batch): add from __future__ import annotations

[ericbn]

Issue number: #4994

Summary

Changes

Add from __future__ import annotations to batch package

User experience

Discussed in #4607

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• Meet tenets criteria
• I have performed a self-review of this change
• Changes have been tested
• Changes are documented
• PR title follows conventional commit semantics

Is this a breaking change?

RFC issue number:

Checklist:

• Migration process documented
• Implement warnings (if it can live side by side)

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[leandrodamascena]

Hey @ericbn! I reverted some changes that included Pydantic models and was failing in Pythoh 3.8/3.9. Can you check please?

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[ericbn]

Given the latest findings, we need to make sure the old typing types are still being used in:

1. Pydantic models
2. Type aliases
3. typing.cast calls

I’ll double check this until Monday.

EDIT: I also suggest we remove the from __future__ import annotations from files where it’s not needed.

[leandrodamascena]

Given the latest findings, we need to make sure the old typing types are still being used in:

1. Pydantic models
2. Type aliases
3. typing.cast calls

I’ll double check this until Monday.

EDIT: I also suggest we remove the from __future__ import annotations from files where it’s not needed.

Perfect! I've added the label do-not-merge.

[ericbn]

I've reviewed all open PRs regarding the items we've listed above, and looks like we're all good.

[leandrodamascena]

APPROVED!